Skip to content

Instantly share code, notes, and snippets.

View 1.27.0.md

Spinnaker Release 1.27.0

Note: This release requires Halyard version 1.45.0 or later.

This release includes fixes, features, and performance improvements across a wide feature set in Spinnaker. This section provides a summary of notable improvements followed by the comprehensive changelog.

Clouddriver

  • Retry capability has been added for kubectl calls. This can be enabled by setting kubernetes.jobExecutor.retries.enabled: true. It is turned off by default.
View release-1.27.x-raw-changelog.md

Clouddriver 5.74.3

Features

  • artifacts: support tokenFile for GitRepoArtifactCredentials and reload auth headers (#5505) (d9f86a91)
  • artifacts: support tokenFile for GitRepoArtifactCredentials and reload auth headers for http (d9f86a91)
  • artifacts: support tokenFile and reload headers tests (d9f86a91)
  • artifacts: support tokenFile and reload headers tests (d9f86a91)
  • aws: Adding support for capacity rebalance (5b3a6196)
  • aws: Add priority to launch template overrides for explicit ordering an
@spinnaker-release
spinnaker-release / 1.26.0.md
Last active Feb 8, 2022
Spinnaker 1.26.x Release Notes
View 1.26.0.md

Spinnaker Release 1.26.0

Note: This release requires Halyard version 1.41.0 or later.

This release includes fixes, features, and performance improvements across a wide feature set in Spinnaker. This section provides a summary of notable improvements followed by the comprehensive changelog.

Curated Changlog

(Breaking Change) Suffix no longer added to jobs created by Kubernetes Run Job stage

As a followup to this change in Spinnaker version 1.22, Spinnaker 1.26 removes the kubernetes.jobs.append-suffix flag. Note that the default value of this flag was false in Spinnaker version >= 1.22. To continue having a random suffix added to the job name, set the metadata.generateName field instead of metadata.name, which causes the Kubernetes API to append a random suffix to the

@spinnaker-release
spinnaker-release / 1.25.0.md
Last active Feb 8, 2022
Spinnaker 1.25.x Release Notes
View 1.25.0.md

Spinnaker Release 1.25.0

Note: This release requires Halyard version 1.41.0 or later.

This release includes fixes, features, and performance improvements across a wide feature set in Spinnaker. This section provides a summary of notable improvements followed by the comprehensive changelog.

Changelog

Clouddriver 7.3.0

@spinnaker-release
spinnaker-release / 1.24.0.md
Last active Sep 6, 2021
Spinnaker 1.24.x Release Notes
View 1.24.0.md

Spinnaker Release 1.24.0

Note: This release requires Halyard version 1.32.0 or later.

This release includes fixes, features, and performance improvements across a wide feature set in Spinnaker. This section provides a summary of notable improvements followed by the comprehensive changelog.

Curated Changlog

Official Docker Registry Has Changed

Official Spinnaker Kubernetes containers have moved from gcr.io/spinnaker-marketplace to

@spinnaker-release
spinnaker-release / 1.23.0.md
Last active Feb 19, 2021
Spinnaker 1.23.x Release Notes
View 1.23.0.md

Spinnaker Release 1.23.0

Note: This release requires Halyard version 1.32.0 or later.

This release includes fixes, features, and performance improvements across a wide feature set in Spinnaker. This section provides a summary of notable improvements followed by the comprehensive changelog.

(Breaking Change) Spinnaker Kubernetes manifest image overwriting with a bound artifact

Spinnaker will now overwrite images in a manifest with a bound artifact if the input manifest's image has a tag on it. The previous behavior was that Spinnaker would only overwrite images in a manifest if the image did not have a tag.

@spinnaker-release
spinnaker-release / 1.22.0.md
Last active Jan 28, 2021
Spinnaker 1.22.x Release Notes
View 1.22.0.md

Spinnaker Release 1.22.0

Note: This release requires Halyard version 1.32.0 or later.

This release includes fixes, features, and performance improvements across a wide feature set in Spinnaker. This section provides a summary of notable improvements followed by the comprehensive changelog.

(Breaking Change) Suffix no longer added to jobs created by Kubernetes Run Job stage

Spinnaker no longer automatically appends a unique suffix to the name of jobs created by the Kubernetes Run Job stage. Prior to this release, if you specified metadata.name: my-job, Spinnaker would update the name to

@spinnaker-release
spinnaker-release / 1.21.0.md
Last active Dec 7, 2020
Spinnaker 1.21.x Release Notes
View 1.21.0.md

Spinnaker Release 1.21.0

Note: This release requires Halyard version 1.32.0 or later.

This release includes fixes, features, and performance improvements across a wide feature set in Spinnaker. Here we share a summary of notable improvements, followed by the comprehensive changelog.

End of Support for the legacy Kubernetes Provider

1.20 was the final release to include support for Spinnaker's legacy Kubernetes (V1) provider. Please migrate all Kubernetes accounts to the standard (V2) provider before upgrading to Spinnaker 1.21.

@spinnaker-release
spinnaker-release / 1.20.0.md
Last active Sep 15, 2020
Spinnaker 1.20.x Release Notes
View 1.20.0.md

Spinnaker Release 1.20

Note: This release requires Halyard version 1.32.0 or later.

This release includes fixes, features, and performance improvements across a wide feature set in Spinnaker. Here we share a summary of notable improvements, followed by the comprehensive changelog.

Kubernetes V2 Run Job Stage

Spinnaker 1.20 no longer automatically adds a unique suffix to the name of jobs. Prior to this release, the Kubernetes V2 Run Job stage added a unique suffix to the name of the deployed job, with no ability to control or configure this behavior.

To continue having a random suffix added to the job name, set the metadata.generateName field instead of metadata.name, which causes the Kubernetes API to append a random suffix to the name.

@spinnaker-release
spinnaker-release / 1.17.0.md
Last active Apr 3, 2020
Spinnaker 1.17.x Release Notes
View 1.17.0.md

Spinnaker Release 1.17.0

This release includes fixes, features, and performance improvements across a wide feature set in Spinnaker. Here we share a summary of notable improvements, followed by the comprehensive changelog.

Git Repo Artifact Support

In 1.17 we’ve added support for representing Git repositories as artifacts. The intent for this type of artifact is to enable us to build features around tools that work with a collection of files rather than a single file, like the Deploy (Manifest) stage. Currently, this artifact type is only supported by the Bake (Manifest) stage when using the Kustomize rendering engine but other areas are being explored to determine where this might make sense. Halyard support for configuring this artifact type is forthcoming. See the proposal for more details.

Improved Kustomize Support

Support for Kustomize has been improved to utilize the Git Repo artifact type which should make it more broadly useable. The pre