v2.27.2 Armory Enterprise Release LTS (Spinnaker™ v1.27.0)

Release notes for Armory Enterprise v2.27.2 LTS

2021/12/14 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 Operator version

To install, upgrade, or configure Armory 2.27.2, use the following Operator version:

  • Armory Operator 1.4.0 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.

This release includes a security fix. For more information, see the Critical Notification that Armory’s Support Team sent out on 14 December 2021, contact your Armory account rep, or see this (login required) Support article: https://support.armory.io/support?id=kb_article_view&sysparm_article=KB0010520.

Breaking changes

Halyard deprecation

Halyard is no longer supported for installing Armory Enterprise 2.27.0 and later. Use the Operator. For more information, see Halyard Deprecation.

Plugin compatibility

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

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

Plugin Version
Armory Agent for Kubernetes Clouddriver Plugin 0.10.0
App Name 0.2.0
AWS Lambda 1.0.9
Evaluate Artifacts 0.1.1
External Accounts 0.2.0
Observability Plugin 1.3.1
Policy Engine 0.2.1-rc

Known issues

Bake failures

The Packer version included with Rosco disregards package overrides that use the -var-file= option. This may cause bakes to fail.

Affected versions: 2.22.2 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.

2.26.x or later: Change the artifact binding behavior in spec.spinnakerConfig.profiles.clouddriver (Operator) or clouddriver-local.yml (Halyard) to the following, which causes artifacts to only bind the version when the tag is missing:

kubernetes:
  artifact-binding:
    docker-image: match-name-only

This setting only binds the version when the tag is missing, such as image: nginx without a version number.

Affected versions: 2.26.x and later

Pipelines as Code GitHub comments

There is a known issue where Pipelines as Code can generate hundreds of comments in a GitHub Pull Request (PR) when updates are made, such as when a module that is used by multiple dinghyfiles gets changed. These comments may prevent the GitHub UI from loading or related API calls may lead to rate limiting.

Affected versions: 2.26.x and later

Workaround:

You can either manually resolve the comments so that you can merge any PRs or turn the notifications that Pipelines as Code sends to GitHub.

For information about about how to disable this functionality, see GitHub Notifications.

Highlighted updates

This release includes a security fix. For more information, see the Critical Notification that Armory’s Support Team sent out on 14 December 2021, contact your Armory account rep, or see this (login required) Support article: https://support.armory.io/support?id=kb_article_view&sysparm_article=KB0010520.

Detailed updates

Bill Of Materials (BOM)

Here’s the BOM for this version.

Expand
version: 2.27.2
timestamp: "2021-12-14 23:38:36"
services:
    clouddriver:
        commit: a9bd461d8e5e862925b4c04f77774da97e2ecd73
        version: 2.27.2
    deck:
        commit: d2a44f00f618e01853ef7890abe1ed6d2ce62c2e
        version: 2.27.2
    dinghy:
        commit: 71f2ed003fe6b75d8e4f43e800725f2ff3a8a1fe
        version: 2.27.2
    echo:
        commit: 5ec4a67ff921c2bdefc776dda03a0780ff853bcf
        version: 2.27.2
    fiat:
        commit: f23a1b97346816afc4e8e85dfc3ac137282af64a
        version: 2.27.2
    front50:
        commit: f6339ea78bf6edc39250289b1a9e5545d53bc94f
        version: 2.27.2
    gate:
        commit: 10936c03e0722b42a8d632f7869e4c1ad29610a6
        version: 2.27.2
    igor:
        commit: 9f4db42f060f6fb45aad4c038525d71528a2f9f5
        version: 2.27.2
    kayenta:
        commit: 1cdf69a42c359a1f12077b6b1cba5606ac3e5daf
        version: 2.27.2
    monitoring-daemon:
        version: 2.26.0
    monitoring-third-party:
        version: 2.26.0
    orca:
        commit: 522655a252c5a1a97f7745fe622ba06bccb99a8c
        version: 2.27.2
    rosco:
        commit: ac6fe57054e435c6058911c4caa177cba5fa64b3
        version: 2.27.2
    terraformer:
        commit: 5e69c32279c6516047eaf6de261d3632095677aa
        version: 2.27.2
dependencies:
    redis:
        version: 2:2.8.4-2
artifactSources:
    dockerRegistry: docker.io/armory

Armory

Armory Rosco - 2.27.1…2.27.2

Dinghy™ - 2.27.1…2.27.2

Armory Kayenta - 2.27.1…2.27.2

Armory Front50 - 2.27.1…2.27.2

Armory Fiat - 2.27.1…2.27.2

Armory Deck - 2.27.1…2.27.2

  • chore(cd): update base deck version to 2021.0.0-20211115175155.release-1.27.x (#1148)

Armory Gate - 2.27.1…2.27.2

  • chore(cd): update base service version to gate:2021.12.14.20.34.14.release-1.27.x (#355)

Armory Orca - 2.27.1…2.27.2

Armory Echo - 2.27.1…2.27.2

Armory Clouddriver - 2.27.1…2.27.2

Terraformer™ - 2.27.1…2.27.2

Armory Igor - 2.27.1…2.27.2


Last modified July 20, 2022: (83f09a79)