Deck 3.2.1
- functions: normalizeFunction expects a Promise (#8468) (f435b50b)
Front50 0.24.1
- provider/Oracle: Cache issue related to Oracle Object Storage (bp #886) (ca2d409b)
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.
The Alicloud, DC/OS, and Oracle cloud providers are excluded from 1.21 because they no longer meet Spinnaker's cloud provider requirements, which include the formation of a Spinnaker SIG. If you are interested in forming a SIG for one of these cloud providers, please comment on the appropriate GitHub issue:
Previously, fixes were merged into release branches at the discretion of the release manager. To increase the transparency of the release process and the safety of the patch release upgrade process, we have documented more explicit patch criteria to determine whether a change is appropriate to cherry-pick into a release branch.
Previously, failures in pipelines that run as stages of other pipelines were
difficult to debug. There is now a modal to surface failed child pipeline
execution details. Enable this functionality by adding the following to your
settings-local.js
:
window.spinnakerSettings.feature.executionMarkerInformationModal = true;
Please report any bugs by opening a GitHub issue. Barring any major issues, this feature will be enabled by default in 1.22. Check out the PR for more details.
1.20
enabled the standard artifacts UI by default, but provided a temporary
legacyArtifactsEnabled
flag to revert to the legacy artifacts UI. This flag
is no longer supported in 1.21, and the standard artifacts UI is the only
available artifacts UI. See this
RFC
for more details.
In 1.22, Spinnaker will no longer automatically append a unique suffix to the name of jobs created by the Kubernetes Run Job stage. Currently, if you specify metadata.name: my-job
, Spinnaker updates the name to my-job-[random-string]
before deploying the job to Kubernetes. As of Spinnaker 1.22, the job's name will be passed through to Kubernetes exactly as supplied.
To continue having a random suffix added to the job name, users should specify the metadata.generateName
field instead of metadata.name
, which will cause the Kubernetes API to append a random suffix to the name.
This change is particularly important for users who are using the preconfigured job stage for Kubernetes, or who are otherwise sharing job stages among different pipelines. In these cases, jobs are often running concurrently, and it is important that each job have a unique name. In order to retain the current behavior, these users will need to manually update their Kubernetes job manifests to use the generateName
field.
Users of Spinnaker 1.21 can opt in to this new behavior by setting kubernetes.jobs.append-suffix: false
in their clouddriver-local.yml
. This behavior will become the default in Spinnaker 1.22 with an ability to opt out. The ability to opt out will be removed in Spinnaker 1.23.
Users are encouraged to update any necessary jobs to specify metadata.generateName
between now and Spinnaker 1.22. Specifying a metadata.generateName
will cause a suffix to be appended, regardless of the above flag, so users can incrementally update their jobs and then opt in to the new behavior once all jobs have been updated. It is not necessary to set the above flag before starting to use the metadata.generateName
field.
BlockDeviceConfig
for c6g/r6g family (d68a92e4)BlockDeviceConfig
for c5a family (eeec3c0c)legacyArtifactsEnabled
setting (f4d41551)skin
and providerVersion
(72af6cc4)/ServiceAccounts
fails when sql is only active provider (225688bf)findAllByIds
was prematurely removed (15d3f44c)main
source set to Java (7186db36)Content-Type
within DataController
(f83fef97)DataController
(2a92287f)skin
and providerVersion
(b2077e2d)commitDelta_closure47
(3b56280f)kayenta
(896fff95)