v2.34.1-rc1 Armory Continuous Deployment Release (Spinnaker™ v1.34.5)

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

2024/08/29 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.34.1-rc1, 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.

Swagger UI endpoint change

API documentation implementing swagger has been upgraded to use Springfox 3.0.0.

Breaking Change: Swagger-ui endpoint changed from /swagger-ui.html to /swagger-ui/index.html.

Kubernetes API version change for client.authentication.k8s.io

kubectl in the latest releases has removed support for external auth flows using the apiVersion: client.authentication.k8s.io/v1alpha1 exec API.

Breaking Change: Update your kubeconfig files to use the v1beta1 apiVersion: client.authentication.k8s.io/v1beta1

Known issues

Highlighted updates

Spring Boot 2.6.15

Spring Boot 2.6 considers session data cached by previous Spring Boot versions invalid. Therefore, users with cached sessions will be unable to log in until the invalid information is removed from the cache.

Open browser windows to Spinnaker are unresponsive after the deployment until they’re reloaded. Once Gate is updated to the new Armory CD version please execute:

$ redis-cli keys "spring:session*" | xargs redis-cli del

on Gate’s redis instance removes the cached session information.

Lambda Operations

Introduced in OSS Spinnaker 1.33.0 and included in the 2.34.0-rc4 release, Armory CD now supports configurable Invocation timeouts and retries for Lambda operations. Previously the SDK would restrict timeouts despite any configuration to 55 seconds.

To set the timeout and retry values, add the following to your clouddriver-local.yml:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15

apiVersion: spinnaker.armory.io/v1alpha2
kind: SpinnakerService
metadata:
  name: spinnaker
spec:
  spinnakerConfig:
    profiles:
      clouddriver:
        aws:
          features:
            lambda:
              enabled: true
          lambda:
            invokeTimeoutMs: 4000000
            retries: 3

Changes in S3 Artifact Store configuration

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 added support for the same feature for the Terraform Integration stage.

In Armory CD version 2.34.0-rc4, the S3 Artifact Store configuration flags have been modified to support either store or retrieval or both of remote artifacts.

Configuration in 2.32.x

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>

Configuration in 2.34.0-rc4 (Store/Get)

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

Configuration in 2.34.0-rc4 (Get only)

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

Dinghy support for delete stale pipelines

Dinghy now support deleting stale pipelines - Any pipelines in the Spinnaker application that are not part of the dinghyfile.

These pipelines are identified and deleted automatically when the dinghyfile is updated and processed. You can set the deleteStalePipelines flag to true in the dinghyfile to enable this feature.

{
  "application": "yourspinnakerapplicationname",
  "deleteStalePipelines": true,
  "pipelines": [
  ]
}

Spinnaker community contributions

There have also been numerous enhancements, fixes, and features across all of Spinnaker’s other services. See the Spinnaker v1.34.5 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: 7602c40d66f8d99254c740ac782fb4c7a8e547db
    version: 2.34.1-rc1
  deck:
    commit: 4e15526f16000326035436c57783415b5e5c1d72
    version: 2.34.1-rc1
  dinghy:
    commit: fbba492fb3d6c116d75f9ca959f6b5d84ab473a6
    version: 2.34.1-rc1
  echo:
    commit: 391b1f4924679a0ce23c216d4b0d8bc4cfdd9ed5
    version: 2.34.1-rc1
  fiat:
    commit: df367d6ed0185b61abcea1e943109503a4b7928b
    version: 2.34.1-rc1
  front50:
    commit: eb8691d3c549c86ba3547b0710828b9f37c62f38
    version: 2.34.1-rc1
  gate:
    commit: f54a45abcf7a622e4233e471723c2b54d3972c5d
    version: 2.34.1-rc1
  igor:
    commit: 0ddc88fc33b097ca8d822e91591218c2216dbbc2
    version: 2.34.1-rc1
  kayenta:
    commit: b8983452be0897fc98a6c47d84f8689a9e0e623b
    version: 2.34.1-rc1
  monitoring-daemon:
    commit: null
    version: 2.26.0
  monitoring-third-party:
    commit: null
    version: 2.26.0
  orca:
    commit: 9385c93a4ce4f30a5484989b0b9913b6cd7e24d6
    version: 2.34.1-rc1
  rosco:
    commit: f0e9fdb04e392820324f5edb72c0ff46b5307701
    version: 2.34.1-rc1
  terraformer:
    commit: d4b6e9f53f3a2b595ce25e0b044318d47fd239b6
    version: 2.34.1-rc1
timestamp: "2024-08-29 12:35:20"
version: 2.34.1-rc1

Armory

Dinghy™ - 2.34.0…2.34.1-rc1

Armory Gate - 2.34.0…2.34.1-rc1

  • chore(cd): update base service version to gate:2024.08.09.02.35.08.release-1.34.x (#744)
  • chore(cd): update base service version to gate:2024.08.10.04.22.27.release-1.34.x (#745)
  • chore(cd): update base service version to gate:2024.08.16.23.57.38.release-1.34.x (#746)
  • chore(cd): update base service version to gate:2024.08.17.03.15.23.release-1.34.x (#747)

Armory Rosco - 2.34.0…2.34.1-rc1

  • chore(cd): update base service version to rosco:2024.08.17.00.00.56.release-1.34.x (#684)

Armory Igor - 2.34.0…2.34.1-rc1

  • chore(cd): update base service version to igor:2024.08.17.03.16.09.release-1.34.x (#623)

Armory Fiat - 2.34.0…2.34.1-rc1

  • chore(cd): update base service version to fiat:2024.08.16.23.56.14.release-1.34.x (#625)

Terraformer™ - 2.34.0…2.34.1-rc1

  • chore(terraformer): Backport fixes (#571)

Armory Kayenta - 2.34.0…2.34.1-rc1

  • chore(cd): update base service version to kayenta:2024.08.08.20.11.17.release-1.34.x (#549)
  • chore(cd): update base service version to kayenta:2024.08.17.05.49.51.release-1.34.x (#552)

Armory Front50 - 2.34.0…2.34.1-rc1

  • chore(cd): update base service version to front50:2024.08.16.23.58.39.release-1.34.x (#708)
  • chore(cd): update base service version to front50:2024.08.18.02.21.08.release-1.34.x (#711)
  • chore(cd): update base service version to front50:2024.08.23.16.11.18.release-1.34.x (#712)

Armory Orca - 2.34.0…2.34.1-rc1

  • chore(cd): update base orca version to 2024.08.17.02.35.16.release-1.34.x (#932)
  • chore(cd): update base orca version to 2024.08.17.03.26.59.release-1.34.x (#933)

Armory Deck - 2.34.0…2.34.1-rc1

  • chore(cd): update base deck version to 2024.0.0-20240808191056.release-1.34.x (#1428)

Armory Echo - 2.34.0…2.34.1-rc1

  • chore(cd): update base service version to echo:2024.08.16.23.59.20.release-1.34.x (#737)
  • chore(cd): update base service version to echo:2024.08.17.03.16.29.release-1.34.x (#738)

Armory Clouddriver - 2.34.0…2.34.1-rc1

  • chore(cd): update base service version to clouddriver:2024.08.08.19.08.20.release-1.34.x (#1157)
  • chore(cd): update base service version to clouddriver:2024.08.17.00.37.38.release-1.34.x (#1160)
  • chore(cd): update base service version to clouddriver:2024.08.17.03.54.14.release-1.34.x (#1161)
  • chore(cd): update base service version to clouddriver:2024.08.17.21.27.20.release-1.34.x (#1163)
  • chore(cd): update base service version to clouddriver:2024.08.18.02.43.56.release-1.34.x (#1165)

Spinnaker

Spinnaker Gate - 1.34.5

  • fix(web/test): stop leaking system properties from FunctionalSpec (#1798) (#1818)
  • fix(core): remove ErrorPageSecurityFilter bean named errorPageSecurityInterceptor (#1817)
  • chore(dependencies): Autobump korkVersion (#1821)
  • chore(dependencies): Autobump fiatVersion (#1822)

Spinnaker Rosco - 1.34.5

  • chore(dependencies): Autobump korkVersion (#1106)

Spinnaker Igor - 1.34.5

  • chore(dependencies): Autobump korkVersion (#1253)
  • chore(dependencies): Autobump fiatVersion (#1250)
  • chore(dependencies): Autobump korkVersion (#1272)
  • chore(dependencies): Autobump fiatVersion (#1273)

Spinnaker Fiat - 1.34.5

  • chore(dependencies): Autobump korkVersion (#1156)
  • chore(dependencies): Autobump korkVersion (#1153)
  • chore(dependencies): Autobump korkVersion (#1177)

Spinnaker Kayenta - 1.34.5

  • fix(stackdriver): handle null timeSeries and empty points (#1047) (#1050)
  • chore(dependencies): Autobump orcaVersion (#1058)

Spinnaker Front50 - 1.34.5

  • chore(dependencies): Autobump korkVersion (#1488)
  • chore(dependencies): Autobump fiatVersion (#1489)
  • fix(gha): only bump halyard on master (#1490) (#1491)
  • fix(front50-gcs): Fix ObjectType filenames for GCS Front50 persistent store (#1493) (#1494)

Spinnaker Orca - 1.34.5

  • chore(dependencies): Autobump korkVersion (#4776)
  • chore(dependencies): Autobump fiatVersion (#4777)

Spinnaker Deck - 1.34.5

  • chore(gcp): Adding STRONG_COOKIE_AFFINITY in gcp LB model (#10124) (#10127)

Spinnaker Echo - 1.34.5

  • chore(dependencies): Autobump korkVersion (#1417)
  • feat(pipelinetriggers): set pipeline-cache.filterFront50Pipelines to true by default (#1416)
  • chore(dependencies): Autobump fiatVersion (#1413)
  • chore(dependencies): Autobump korkVersion (#1440)
  • chore(dependencies): Autobump fiatVersion (#1441)

Spinnaker Clouddriver - 1.34.5

  • chore(gcp): Adding STRONG_COOKIE_AFFINITY in gcp LB model (#6259) (#6262)
  • chore(dependencies): Autobump korkVersion (#6266)
  • chore(dependencies): Autobump fiatVersion (#6267)
  • fix(gha): only bump halyard on master (#6268) (#6269)
  • fix(gha): remove whitespace from BRANCH in release.yml (#6271) (#6272)

Last modified November 7, 2024: (8eba3bc5)