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.
kubernetes.jobExecutor.retries.enabled: true. It is turned off by default.
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.
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
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.
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.
Official Spinnaker Kubernetes containers have moved from
gcr.io/spinnaker-marketplace to
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.
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.
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.
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
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.
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.
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.
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.
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.
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.
Support for Kustomize has been improved to utilize the Git Repo artifact type which should make it more broadly useable. The pre