v2.32.1-rc3 Armory Continuous Deployment Release (Spinnaker™ v1.32.4)

Release notes for Armory Continuous Deployment v2.32.1-rc3. A beta release is not meant for installation in production environments.

2024/03/12 release notes

Disclaimer

This pre-release software is to allow limited access to test or beta versions of the Armory services (“Services”) and to provide feedback and comments to Armory regarding the use of such Services. By using Services, you agree to be bound by the terms and conditions set forth herein.

Your Feedback is important and we welcome any feedback, analysis, suggestions and comments (including, but not limited to, bug reports and test results) (collectively, “Feedback”) regarding the Services. Any Feedback you provide will become the property of Armory and you agree that Armory may use or otherwise exploit all or part of your feedback or any derivative thereof in any manner without any further remuneration, compensation or credit to you. You represent and warrant that any Feedback which is provided by you hereunder is original work made solely by you and does not infringe any third party intellectual property rights.

Any Feedback provided to Armory shall be considered Armory Confidential Information and shall be covered by any confidentiality agreements between you and Armory.

You acknowledge that you are using the Services on a purely voluntary basis, as a means of assisting, and in consideration of the opportunity to assist Armory to use, implement, and understand various facets of the Services. You acknowledge and agree that nothing herein or in your voluntary submission of Feedback creates any employment relationship between you and Armory.

Armory may, in its sole discretion, at any time, terminate or discontinue all or your access to the Services. You acknowledge and agree that all such decisions by Armory are final and Armory will have no liability with respect to such decisions.

YOUR USE OF THE SERVICES IS AT YOUR OWN RISK. THE SERVICES, THE ARMORY TOOLS AND THE CONTENT ARE PROVIDED ON AN “AS IS” BASIS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. ARMORY AND ITS LICENSORS MAKE NO REPRESENTATION, WARRANTY, OR GUARANTY AS TO THE RELIABILITY, TIMELINESS, QUALITY, SUITABILITY, TRUTH, AVAILABILITY, ACCURACY OR COMPLETENESS OF THE SERVICES, THE ARMORY TOOLS OR ANY CONTENT. ARMORY EXPRESSLY DISCLAIMS ON ITS OWN BEHALF AND ON BEHALF OF ITS EMPLOYEES, AGENTS, ATTORNEYS, CONSULTANTS, OR CONTRACTORS ANY AND ALL WARRANTIES INCLUDING, WITHOUT LIMITATION (A) THE USE OF THE SERVICES OR THE ARMORY TOOLS WILL BE TIMELY, UNINTERRUPTED OR ERROR-FREE OR OPERATE IN COMBINATION WITH ANY OTHER HARDWARE, SOFTWARE, SYSTEM OR DATA, (B) THE SERVICES AND THE ARMORY TOOLS AND/OR THEIR QUALITY WILL MEET CUSTOMER”S REQUIREMENTS OR EXPECTATIONS, (C) ANY CONTENT WILL BE ACCURATE OR RELIABLE, (D) ERRORS OR DEFECTS WILL BE CORRECTED, OR (E) THE SERVICES, THE ARMORY TOOLS OR THE SERVER(S) THAT MAKE THE SERVICES AVAILABLE ARE FREE OF VIRUSES OR OTHER HARMFUL COMPONENTS. CUSTOMER AGREES THAT ARMORY SHALL NOT BE RESPONSIBLE FOR THE AVAILABILITY OR ACTS OR OMISSIONS OF ANY THIRD PARTY, INCLUDING ANY THIRD-PARTY APPLICATION OR PRODUCT, AND ARMORY HEREBY DISCLAIMS ANY AND ALL LIABILITY IN CONNECTION WITH SUCH THIRD PARTIES.

IN NO EVENT SHALL ARMORY, ITS EMPLOYEES, AGENTS, ATTORNEYS, CONSULTANTS, OR CONTRACTORS BE LIABLE UNDER THIS AGREEMENT FOR ANY CONSEQUENTIAL, SPECIAL, LOST PROFITS, INDIRECT OR OTHER DAMAGES, INCLUDING BUT NOT LIMITED TO LOST PROFITS, LOSS OF BUSINESS, COST OF COVER WHETHER BASED IN CONTRACT, TORT (INCLUDING NEGLIGENCE), OR OTHERWISE, EVEN IF ARMORY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES AND NOTWITHSTANDING ANY FAILURE OF ESSENTIAL PURPOSE OF ANY LIMITED REMEDY. IN ANY EVENT, ARMORY, ITS EMPLOYEES’, AGENTS’, ATTORNEYS’, CONSULTANTS’ OR CONTRACTORS’ AGGREGATE LIABILITY UNDER THIS AGREEMENT FOR ANY CLAIM SHALL BE STRICTLY LIMITED TO $100.00. SOME STATES DO NOT ALLOW THE LIMITATION OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATION OR EXCLUSION MAY NOT APPLY TO YOU.

You acknowledge that Armory has provided the Services in reliance upon the limitations of liability set forth herein and that the same is an essential basis of the bargain between the parties.

Required Armory Operator version

To install, upgrade, or configure Armory CD 2.32.1-rc3, 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

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.1-rc3
  deck:
    commit: e7c8c0982afe9a49ab6c3d230f3aaa38e874eb30
    version: 2.32.1-rc3
  dinghy:
    commit: f5b14ffba75721322ada662f2325e80ec86347de
    version: 2.32.1-rc3
  echo:
    commit: 9d2abeeea4341e5ba94654925ba6488a9038af3f
    version: 2.32.1-rc3
  fiat:
    commit: 3f3fe6bf09708847a0f853bc74f6755920a4312b
    version: 2.32.1-rc3
  front50:
    commit: ba318cd2c445f14e5d6c3db87fa1658549385403
    version: 2.32.1-rc3
  gate:
    commit: dd64887668a2e2212667ca942e0bfd303aa34c60
    version: 2.32.1-rc3
  igor:
    commit: 9339ab63ab3d85ebcb00131033d19f26ad436f05
    version: 2.32.1-rc3
  kayenta:
    commit: bccd150fcc8a7cb7df537ec6269bce5d2843c703
    version: 2.32.1-rc3
  monitoring-daemon:
    commit: null
    version: 2.26.0
  monitoring-third-party:
    commit: null
    version: 2.26.0
  orca:
    commit: 9d45d87956abd9aad29ef8f9858e602e72d78c3c
    version: 2.32.1-rc3
  rosco:
    commit: dfe611ffdd2cf9ae7c524fb9970af47350ca5e96
    version: 2.32.1-rc3
  terraformer:
    commit: 6dbdb8b4c277cca4285b4d29d10f6cf3765f7590
    version: 2.32.1-rc3
timestamp: "2024-03-12 14:53:28"
version: 2.32.1-rc3

Armory

Armory Front50 - 2.32.1-rc2…2.32.1-rc3

chore(cd): update base service version to front50:2024.03.08.16.52.13.release-1.32.x (#666)
chore(cd): update base service version to front50:2024.03.08.19.18.53.release-1.32.x (#667)

Armory Clouddriver - 2.32.1-rc2…2.32.1-rc3

chore(cd): update base service version to clouddriver:2024.03.08.19.52.28.release-1.32.x (#1091)

Armory Deck - 2.32.1-rc2…2.32.1-rc3

Armory Orca - 2.32.1-rc2…2.32.1-rc3

chore(cd): update base orca version to 2024.03.08.16.54.30.release-1.32.x (#840)
chore(cd): update base orca version to 2024.03.08.19.21.42.release-1.32.x (#841)

Dinghy™ - 2.32.1-rc2…2.32.1-rc3

Armory Gate - 2.32.1-rc2…2.32.1-rc3

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

Armory Rosco - 2.32.1-rc2…2.32.1-rc3

chore(cd): update base service version to rosco:2024.03.08.16.49.31.release-1.32.x (#650)

Armory Echo - 2.32.1-rc2…2.32.1-rc3

chore(cd): update base service version to echo:2024.03.08.16.50.19.release-1.32.x (#697)
chore(cd): update base service version to echo:2024.03.08.19.17.18.release-1.32.x (#698)

Terraformer™ - 2.32.1-rc2…2.32.1-rc3

Armory Fiat - 2.32.1-rc2…2.32.1-rc3

chore(cd): update base service version to fiat:2024.03.08.16.48.59.release-1.32.x (#590)

Armory Kayenta - 2.32.1-rc2…2.32.1-rc3

chore(cd): update base service version to kayenta:2024.03.08.20.48.11.release-1.32.x (#525)

Armory Igor - 2.32.1-rc2…2.32.1-rc3

chore(cd): update base service version to igor:2024.03.08.16.52.17.release-1.32.x (#584)
chore(cd): update base service version to igor:2024.03.08.19.18.39.release-1.32.x (#585)

Spinnaker

Spinnaker Front50 - 1.32.4

chore(dependencies): Autobump korkVersion (#1439)
chore(dependencies): Autobump fiatVersion (#1440)

Spinnaker Clouddriver - 1.32.4

chore(dependencies): Autobump korkVersion (#6169)
chore(dependencies): Autobump fiatVersion (#6170)

Spinnaker Deck - 1.32.4

Spinnaker Orca - 1.32.4

chore(dependencies): Autobump korkVersion (#4667)
chore(dependencies): Autobump fiatVersion (#4668)

Spinnaker Gate - 1.32.4

chore(dependencies): Autobump korkVersion (#1773)
chore(dependencies): Autobump fiatVersion (#1774)

Spinnaker Rosco - 1.32.4

chore(dependencies): Autobump korkVersion (#1077)

Spinnaker Echo - 1.32.4

chore(dependencies): Autobump korkVersion (#1398)
chore(dependencies): Autobump fiatVersion (#1399)

Spinnaker Fiat - 1.32.4

chore(dependencies): Autobump korkVersion (#1145)

Spinnaker Kayenta - 1.32.4

chore(dependencies): Autobump orcaVersion (#1023)

Spinnaker Igor - 1.32.4

chore(dependencies): Autobump korkVersion (#1235)
chore(dependencies): Autobump fiatVersion (#1236)

Feedback

Was this page helpful?

Thank you for letting us know!

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

Last modified March 12, 2024: (4741dc92)