v2.32.2 Armory Continuous Deployment Release (Spinnaker™ v1.32.4)

Release notes for Armory Continuous Deployment v2.32.2.

2024/04/30 release notes

Note: If you experience production issues after upgrading Armory Continuous Deployment, roll back to a previous working version and report issues to http://go.armory.io/support.

Required Armory Operator version

To install, upgrade, or configure Armory CD 2.32.2, use Armory Operator 1.8.6 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.

AWS Lambda plugin migrated to OSS

Starting from Armory version 2.32.0 (OSS version 1.32.0), the AWS Lambda plugin has been migrated to OSS codebase. If you are using the AWS Lambda plugin, you will need to disable/remove it when upgrading to Armory version 2.32.0+ to avoid compatibility issues.

Additionally, the AWS Lambda stages are now enabled using the Deck feature flag feature.lambdaAdditionalStages = true; as shown in the configuration block below.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
apiVersion: spinnaker.armory.io/v1alpha2
kind: SpinnakerService
metadata:
  name: spinnaker
spec:
  spinnakerConfig:
    profiles:
      deck:
        settings-local.js: |
          ...
          window.spinnakerSettings.feature.functions = true;
          // Enable the AWS Lambda pipeline stages in Deck using the feature flag
          window.spinnakerSettings.feature.lambdaAdditionalStages = true; 
          ...          
      clouddriver:
        aws:
          enabled: true
          features:
            lambda:
              enabled: true
      ## Remove the AWS Lambda plugin from the Armory CD configuration.
      #gate:
      #  spinnaker:
      #    extensibility:
      #      deck-proxy:
      #        enabled: true
      #        plugins:
      #          Aws.LambdaDeploymentPlugin:
      #            enabled: true
      #            version: <version>
      #      repositories:
      #        awsLambdaDeploymentPluginRepo:
      #          url: https://raw.githubusercontent.com/spinnaker-plugins/aws-lambda-deployment-plugin-spinnaker/master/plugins.json  
      #orca:
      #  spinnaker:
      #    extensibility:
      #      plugins:
      #        Aws.LambdaDeploymentPlugin:
      #          enabled: true
      #          version: <version>
      #          extensions:
      #            Aws.LambdaDeploymentStage:
      #              enabled: true
      #      repositories:
      #        awsLambdaDeploymentPluginRepo:
      #          id: awsLambdaDeploymentPluginRepo
      #          url: https://raw.githubusercontent.com/spinnaker-plugins/aws-lambda-deployment-plugin-spinnaker/master/plugins.json

Related OSS PRs:

Known issues

Highlighted updates

Terraformer support for AWS S3 Artifact Store

OSS Spinnaker 1.32.0 introduced support for artifact storage with AWS S3. This feature compresses embdedded/base64 artifacts to remote/base64 and uploads them to an AWS S3 bucket significantly reducing the artifact size in the execution context.

Armory version 2.32.0 adds support for the same feature for the Terraform Integration stage.

Note: The artifact-store feature is disabled by default. To enable the artifact-store feature the following configuration is required:

apiVersion: spinnaker.armory.io/v1alpha2
kind: SpinnakerService
metadata:
  name: spinnaker
spec:
  spinnakerConfig:
    profiles:
      spinnaker:
        artifact-store:
        enabled: true
        s3:
          enabled: true
          region: <S3Bucket Region>
          bucket: <S3Bucket Name>

When enabling the artifact-store feature it is recommended to deploy the services in this order:

Clouddriver service
Terraformer service
Orca service
Rosco service

Enable Jenkins job triggers for jobs located sub-folders

When defining a Jenkins job in a sub-folder, the path contains forward slashes. By enabling this feature, Armory CD will be able to trigger Jenkins jobs located in sub-folders, correctly matching the job path.

apiVersion: spinnaker.armory.io/v1alpha2
kind: SpinnakerService
metadata:
  name: spinnaker
spec:
  spinnakerConfig:
    profiles:
      echo:
        feature:
          igor:
            jobNameAsQueryParameter: true
      orca:
        feature:
          igor:
            jobNameAsQueryParameter: true
      igor:
        feature:
          igor:
            jobNameAsQueryParameter: true

Pipeline As Code: Bitbucket fallback support for default branch

By default, Dinghy uses the master branch in your repository and fallbacks to main if master doesn’t exist. If you wish to use a different branch in your repository, you can configure that using the repoConfig tag in your YAML configuration.

apiVersion: spinnaker.armory.io/v1alpha2
kind: SpinnakerService
metadata:
  name: spinnaker
spec:
  spinnakerConfig:
    profiles:
      dinghy:
        repoConfig:
        - branch: some_branch
          provider: bitbucket-server
          repo: my-bitbucket-repository

Performance improvements for the search executions API operations

The search executions API operations have been optimized to improve performance and reduce the time taken to search for pipelines by triggerType or eventId.

RunJob stage improvement

RunJob stage now persist any External Log links after the deletion of the pods. This enhancement ensures that the External Log links are available even after the pods are deleted.

Spinnaker community contributions

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

Detailed updates

Bill Of Materials (BOM)

Expand to see the BOM

artifactSources:
  dockerRegistry: docker.io/armory
dependencies:
  redis:
    commit: null
    version: 2:2.8.4-2
services:
  clouddriver:
    commit: b29acea67a40b4145431137ba96454c1d1bf0d73
    version: 2.32.2
  deck:
    commit: 13f331421b292db61f14392e6932880aa5c49f25
    version: 2.32.2
  dinghy:
    commit: f5b14ffba75721322ada662f2325e80ec86347de
    version: 2.32.2
  echo:
    commit: 9d2abeeea4341e5ba94654925ba6488a9038af3f
    version: 2.32.2
  fiat:
    commit: 5e1839ef81812c439fb37b411bd3b381131c8c40
    version: 2.32.2
  front50:
    commit: ba318cd2c445f14e5d6c3db87fa1658549385403
    version: 2.32.2
  gate:
    commit: c6654ca6e316eef474c59296120d3f9f34eb0bdf
    version: 2.32.2
  igor:
    commit: 9339ab63ab3d85ebcb00131033d19f26ad436f05
    version: 2.32.2
  kayenta:
    commit: bccd150fcc8a7cb7df537ec6269bce5d2843c703
    version: 2.32.2
  monitoring-daemon:
    commit: null
    version: 2.26.0
  monitoring-third-party:
    commit: null
    version: 2.26.0
  orca:
    commit: aa898e512f93921b8786ea790bfe1cb5abc12f2b
    version: 2.32.2
  rosco:
    commit: dfe611ffdd2cf9ae7c524fb9970af47350ca5e96
    version: 2.32.2
  terraformer:
    commit: 2dc7666ca2d25acb85ab2b9f8efc864599061c45
    version: 2.32.2
timestamp: "2024-04-25 15:56:08"
version: 2.32.2

Armory

Armory Clouddriver - 2.32.1…2.32.2

Armory Kayenta - 2.32.1…2.32.2

Armory Echo - 2.32.1…2.32.2

Armory Deck - 2.32.1…2.32.2

chore(cd): update base deck version to 2024.0.0-20240416232157.release-1.32.x (#1400)
chore(cd): update base deck version to 2024.0.0-20240425133704.release-1.32.x (#1403)
chore(cd): update base deck version to 2024.0.0-20240425135304.release-1.32.x (#1404)

Armory Fiat - 2.32.1…2.32.2

fix(build): Updating vault addr for gradle build (#597) (#598)

Armory Gate - 2.32.1…2.32.2

chore(cd): update base service version to gate:2024.03.25.21.57.21.release-1.32.x (#712)

Terraformer™ - 2.32.1…2.32.2

fix(tf-show): Reverting go-cmd implementation (#551) (#552)
Build: Removing full history fetch (#553) (#554)
Updating Dockerfile with harness email list and pull from Dockerhub (#550) (#556)
Fixing Dockerfile with missing tools (#557) (#558)
fix(build): Refarctoring Dockerfile to fix build failures (#559) (#560)
fix(build): Fixing Dockerfile for multi-build process (#561) (#562)

Armory Rosco - 2.32.1…2.32.2

Dinghy™ - 2.32.1…2.32.2

Armory Orca - 2.32.1…2.32.2

chore(cd): update base orca version to 2024.03.26.22.19.53.release-1.32.x (#856)
chore(cd): update base orca version to 2024.04.02.15.59.15.release-1.32.x (#860)
chore(cd): update base orca version to 2024.04.15.20.03.44.release-1.32.x (#865)
chore(cd): update base orca version to 2024.04.15.22.28.52.release-1.32.x (#867)

Armory Igor - 2.32.1…2.32.2

Armory Front50 - 2.32.1…2.32.2

Spinnaker

Spinnaker Clouddriver - 1.32.4

Spinnaker Kayenta - 1.32.4

Spinnaker Echo - 1.32.4

Spinnaker Deck - 1.32.4

fix(runJobs): Persist External Log links after the deletion of the pods (#10081) (#10084)
fix(pipelineGraph): Handling exception when requisiteStageRefIds is not defined (#10086) (#10089)
fix(lambdaStages): Exporting Lambda stages based on the feature flag settings (#10085) (#10092)

Spinnaker Fiat - 1.32.4

Spinnaker Gate - 1.32.4

fix(core): RetrofitError thrown on login (#1737) (#1779)

Spinnaker Rosco - 1.32.4

Spinnaker Orca - 1.32.4

feat(servergroup): Allow users to opt-out of the target desired size check when verifying if the instances scaled up or down successfully (#4649) (#4653)
fix(queue): Fix ZombieExecutionCheckingAgent to handle queues with more than 100 items (#4648) (#4683)
fix(explicitRollback): Add configurable timeout for serverGroup lookup from Clouddriver API (#4686) (#4690)
perf(sql): Optimise searchForPipelinesByTrigger LIMIT and OFFSET SQL query (#4698) (#4699)
fix(SqlExecutionRepository): fixed bug in sql repository in orca-sql … (backport #4697) (#4701)

Spinnaker Igor - 1.32.4

Spinnaker Front50 - 1.32.4

Feedback

Was this page helpful?

Thank you for letting us know!

Sorry to hear that. Please tell us how we can improve.

Last modified May 10, 2024: (50677c9b)