v2.30.5 Armory Continuous Deployment LTS Release (Spinnaker™ v1.30.4)

2023/11/10 Release Notes

Note: If you’re experiencing production issues after upgrading Spinnaker, rollback to a previous working version and please report issues to http://go.armory.io/support.

Required Armory Operator version

To install, upgrade, or configure Armory 2.30.5, use Armory Operator 1.70 or later.

Security

Armory scans the codebase as we develop and release software. Contact your Armory account representative for information about CVE scans for this release.

Breaking changes

Breaking changes are kept in this list for 3 minor versions from when the change is introduced. For example, a breaking change introduced in 2.21.0 appears in the list up to and including the 2.24.x releases. It would not appear on 2.25.x release notes.

Orca requires RDBMS configured for UTF-8 encoding

Impact

• 2.28.6 migrates to the AWS MySQL driver from the OSS MySQL drivers. This change is mostly seamless, but we’ve identified one breaking change. If your database was created without utf8mb4 you will see failures after this upgrade. utf8mb4 is the recommended DB format for any Spinnaker database, and we don’t anticipate most users who’ve followed setup instructions to encounter this failure. However, we’re calling out this change as a safeguard.

Introduced in: Armory CD 2.28.6

Update kubectl to 1.20

Impact

With 2.28 of Spinnaker, we’ve updated the kubectl binary to a 1.20 release. You may have potential caching issues as a result due to certain resources in Kubernetes being removed and/or no longer supported. Look for failures in your log files and exclude resources that don’t match your target cluster. For example, adding “PodPreset” to the “omitKinds” on your Kubernetes account configs would cause Spinnaker to skip trying to cache resources that no longer be able to be cached in newer kubernetes releases.

Introduced in: Armory CD 2.28.0

Plugin compatibility

Due to changes in the underlying services, older versions of some plugins may not work with Armory CD 2.30.x or later.

The following table lists the plugins and their required minimum version:

Known issues

Pipelines-as-Code multipleBranchesEnabled: false not working as expected

When multipleBranchesEnabled: false, you may notice that the configuration multipleBranchesEnabled is never set to even though it is set to false under the Dinghy profiles settings. This may cause dinghyfile changes on the master/main branch to be pushed unexpectedly.

You can read more about this issue in the KB article.

Affected versions: Armory CD 2.30.3, 2.30.4, 2.30.5

Clouddriver and Spring Cloud

The Spring Boot version has been upgraded, introducing a backwards incompatible change to the way configuration is loaded in Spinnaker. Users will need to set the spring.cloud.config.enabled property to true in the service settings of Clouddriver to preserve existing behavior. All of the other configuration blocks remain the same.

Affected versions: Armory CD 2.30.0 and later

SpEL expressions and artifact binding

There is an issue where it appears that SpEL expressions are not being evaluated properly in artifact declarations (such as container images) for events such as the Deploy Manifest stage. What is actually happening is that an artifact binding is overriding the image value.

Workaround:

2.27.x or later: Disable artifact binding by adding the following parameter to the stage JSON: enableArtifactBinding: false. This setting only binds the version when the tag is missing, such as image: nginx without a version number.

Affected versions: Armory CD 2.27.x and later

Deprecations

Reference Feature Deprecations and end of support

Early access features enabled by default

Automatically cancel Jenkins jobs

You now have the ability to cancel triggered Jenkins jobs when a Spinnaker pipeline is canceled, giving you more control over your full Jenkins workflow. Learn more about Jenkins + Spinnaker in this Spinnaker changelog.

Enhanced BitBucket Server pull request handling

Trigger Spinnaker pipelines natively when pull requests are opened in BitBucket with newly added events including PR opened, deleted, and declined. See Triggering pipelines with Bitbucket Server in the Spinnaker docs for details

Early access features enabled manually

Helm Parameters

Spinnaker users baking Helm charts can now use SpEL expression parameters for API Version and Kubernetes Version in the Bake Manifest stage so that they can conditionally deploy different versions of artifacts depending on the target cluster API and K8s versions. To learn more about this exciting new feature, visit Helm Parameters.

Dynamic rollback timeout

To make the dynamic timeout available, you need to enable the feature flag in Orca and Deck. You need to add this block to orca.yml file if you want to enable the dynamic rollback timeout feature:

rollback:
  timeout:
    enabled: true

On the Orca side, the feature flag overrides the default value rollback timeout - 5 min - with a UI input from the user.

On the Deck side, the feature flag enhances the Rollback Cluster stage UI with timeout input.

window.spinnakerSettings.feature.dynamicRollbackTimeout = true;

The default is used if there is no value set in the UI.

Run Pipelines-as-Code with permissions scoped to a specific service account

Enhancing Pipelines-as-Code to upsert pipeline using an Orca call instead of a Front50 call, to mimic the calls from Deck. By default, it is disabled. Enabling can be achieved by setting the following in dinghy.yml:

upsertPipelineUsingOrcaTaskEnabled: true

Pipelines-as-Code PR checks

This feature, when enabled, verifies if the author of a commit that changed app parameters has sufficient WRITE permission for that app. You can specify a list of authors whose permissions are not valid. This option’s purpose is to skip permissions checks for bots and tools.

See Permissions check for a commit for details.

Pipelines-as-Code multi-branch enhancement

Now you can configure Pipeline-as-Code to pull Pipelines-as-Code files from multiple branches on the same repo. Cut out the tedious task of managing multiple repos; have a single repo for Spinnaker application pipelines. See Multiple branches for how to enable and configure this feature.

Terraform template fix

Armory fixed an issue with SpEL expression failures appearing while using Terraformer to serialize data from a Terraform Plan execution. With this feature flag fix enabled, you are able to use the Terraform template file provider. Open a support ticket if you need this fix.

Highlighted updates

Echo

• Fixed an issue where Echo didn’t start in GKE.

Orca

• Addressed an issue where artifacts between parent/child pipeline executions were binding incorrectly.

Deck

• Updated Lambda Function runtime options.

Spinnaker Community Contributions

There have also been numerous enhancements, fixes, and features across all of Spinnaker’s other services. See the Spinnaker v1.30.4 changelog for details.

Detailed updates

Bill Of Materials (BOM)

Here’s the BOM for this version.

artifactSources:
  dockerRegistry: docker.io/armory
dependencies:
  redis:
    commit: null
    version: 2:2.8.4-2
services:
  clouddriver:
    commit: 767aa739e9c38d2ec7822e9e9a1838b69a56d4c0
    version: 2.30.5
  deck:
    commit: b14f5660fbe9cde883dfaf25442a1e8cfe0c27b0
    version: 2.30.5
  dinghy:
    commit: a3b59d9e4b810cc968d0f5e8e8370e1670574768
    version: 2.30.5
  echo:
    commit: ea2081903be070da4b217a4c54d070f1503e6d00
    version: 2.30.5
  fiat:
    commit: 5d44e1f53d2f33b17f8decfb057a18cfe4b6fa08
    version: 2.30.5
  front50:
    commit: 5d9bb31f65f96087be30ce96cea1b6d481a6bef4
    version: 2.30.5
  gate:
    commit: 5758316afba1260d2012730c471fd461819e7f39
    version: 2.30.5
  igor:
    commit: 3123451525458f96548859b9bf2b15c89810f577
    version: 2.30.5
  kayenta:
    commit: 1d2f5193ec681b5122fe7c34da6bbd569da8e0b8
    version: 2.30.5
  monitoring-daemon:
    commit: null
    version: 2.26.0
  monitoring-third-party:
    commit: null
    version: 2.26.0
  orca:
    commit: fdac510ea4f54b33abafbc840d7380100c6ab689
    version: 2.30.5
  rosco:
    commit: 7907c80fd9ca1d956d5927a3e190617671b7e012
    version: 2.30.5
  terraformer:
    commit: 249e7be18074af100212ddd554d9fb35afd65873
    version: 2.30.5
timestamp: "2023-11-08 19:09:49"
version: 2.30.5

Armory

Armory Clouddriver - 2.30.4…2.30.5

Armory Orca - 2.30.4…2.30.5

• chore(cd): update base orca version to 2023.11.06.18.16.22.release-1.30.x (#762)
• chore(cd): update base orca version to 2023.11.07.00.08.28.release-1.30.x (#764)

Armory Igor - 2.30.4…2.30.5

Armory Rosco - 2.30.4…2.30.5

Armory Gate - 2.30.4…2.30.5

Armory Front50 - 2.30.4…2.30.5

Armory Fiat - 2.30.4…2.30.5

Armory Kayenta - 2.30.4…2.30.5

Terraformer™ - 2.30.4…2.30.5

Armory Echo - 2.30.4…2.30.5

• fix: Upgrade grpc-netty-shaded to address the service initialization failure issue. (#647)

Dinghy™ - 2.30.4…2.30.5

Armory Deck - 2.30.4…2.30.5

• chore(cd): update base deck version to 2023.0.0-20231024161913.release-1.30.x (#1364)

Spinnaker

Spinnaker Clouddriver - 1.30.4

Spinnaker Orca - 1.30.4

• fix(artifacts): Parent and child pipeline artifact resolution (backport #4575) (#4581)
• fix(artifacts): Automated triggers with artifact constraints are broken if you have 2 or more of the same type (backport #4579) (#4586)

Spinnaker Igor - 1.30.4

Spinnaker Rosco - 1.30.4

Spinnaker Gate - 1.30.4

Spinnaker Front50 - 1.30.4

Spinnaker Fiat - 1.30.4

Spinnaker Kayenta - 1.30.4

Spinnaker Echo - 1.30.4

Spinnaker Deck - 1.30.4

• fix: Updating Lambda functions available Runtimes (#10055) (#10056)