v2.23.3 Armory Continuous Deployment Release (Spinnaker™ v1.23.5)

Release notes for Armory Continuous Deployment v2.23.3

2021/01/06 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 Halyard or Operator version

To install, upgrade, or configure Armory 2.23.3, use one of the following tools:

Armory-extended Halyard 1.10 or later
Armory Operator 1.2.1 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.

Suffix no longer added to jobs created by Kubernetes Run Job stage

Spinnaker no longer automatically appends a unique suffix to the name of jobs created by the Kubernetes Run Job stage. Prior to this release, if you specified metadata.name: my-job, Spinnaker updates the name to my-job-[random-string] before deploying the job to Kubernetes. As of this release, the job’s name will be passed through to Kubernetes exactly as supplied.

To continue having a random suffix added to the job name, set the metadata.generateName field instead of metadata.name, which causes the Kubernetes API to append a random suffix to the name.

This change is particularly important for users who are using the preconfigured job stage for Kubernetes or are sharing job stages among different pipelines. In these cases, jobs often running concurrently, and it is important that each job have a unique name. In order to retain the previous behavior, manually update your Kubernetes job manifests to use the generateName field.

Previously, this behavior was opt-in.

Impact

As of Armory 2.22, this behavior is the default. Users can still opt out of the new behavior by setting kubernetes.jobs.append-suffix: true in clouddriver-local.yml. This causes Spinnaker to continue to append a suffix to the name of jobs as in prior releases.

The ability to opt out of the new behavior will be removed in Armory 2.23 (OSS 1.23). The above setting will have no effect, and Spinnaker will no longer append a suffix to job names. We recommended that 2.22 users note which jobs are using the old behavior and prepare to remove the setting before upgrading to Armory 2.23 in the future.

Introduced in: Armory 2.22

ManifestForceCacheRefreshTask removed from Orca

When you upgrade to 2.23.0 or later, you might encounter the following error:

2021-01-29 23:57:19.691 ERROR 1 --- [    scheduler-2] c.netflix.spinnaker.q.redis.RedisQueue   : Failed to read message 8f072714f1df6dbf3af93a4f4fe4cae2, requeuing...
com.fasterxml.jackson.databind.JsonMappingException: No task found for 'com.netflix.spinnaker.orca.clouddriver.tasks.manifest.ManifestForceCacheRefreshTask' (through reference chain: com.netflix.spinnaker.orca.q.RunTask["taskType"])

The ManifestForceCacheRefreshTask task is no longer a required task when deploying a manifest. In earlier releases, forcing the cache to refresh was part of the deployment process for manifests. Because of this change, if a task was running or retried before the upgrade, the error shows up in logs as an exception.

Workaround

Before starting, make sure that you have access to the Redis instance that Orca uses.

To resolve this issue, delete the message from the queue:

Verify that there are pipeline execution failure messages that contain ManifestForceCacheRefreshTask:

Redis

hgetall orca.task.queue.messages

The command returns information similar to the following:

1) "93ac65e03399a4cfd3678e1355936ab2"
2) "{\"kind\":\"runTask\",\"executionType\":\"PIPELINE\",\"executionId\":\"01EVFCCDG3Q2209E0Z1QTNC0FS\",   \"application\":\"armoryhellodeploy\",\"stageId\":\"01EVFCCDG3TJ7AFPYEJT1N8RDJ\",\"taskId\":\"5\",\"taskType\":\"com.netflix.spinnaker.   orca.clouddriver.tasks.manifest.ManifestForceCacheRefreshTask\",\"attributes\":[{\"kind\":\"attempts\",\"attempts\":1}],   \"ackTimeoutMs\":600000}"

Delete the message(s):
Redis
```
hdel orca.task.queue.messages 
```
The command returns information similar to the following:
```
93ac65e03399a4cfd3678e1355936ab2
(integer) 1
```

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

Zombie Executions

Starting in Spinnaker 2.23.0, ManifestForceCacheRefreshTask was removed, as Kubernetes manifest related stages now do live lookups. While upgrading to Spinnaker 2.23.0 or later, if there is a running pipeline that contains a Kubernetes manifest related stage, it becomes a zombie execution. This causes Orca, Spinnaker’s orchestration service, to fail to complete any Kubernetes manifest related stage in that pipeline.

Workarounds:

To resolve the issue, cancel any zombie executions. For information about how to cancel them, see the Orca Zombie Execution runbook.

Affected versions: 2.23.0 and later

Lambda UI issue

There is a UI bug related to the caching agent that prevents Lambda functions from being displayed in the UI when there are no other clusters associated with the Application. In other words, in order for the function to show up in “Functions” tab, there needs to be a cluster (such as an AWS ASG/EC2 instance) deployed for that application.

Affected versions: 2.23.0 (1.23.0) - 2.26.2 Fixed version: 2.26.3

AWS image caching

There is an issue where Clouddriver fails to cache images that belong to the first account (alphabetically) for each region. For example, in a region with accounts named Edith, Milton, and Pixel, Edith’s images do not get cached.

Affected versions: 2.23.3 and earlier

Fixed versions: 2.24.0, 2.23.4

Workaround:

Two workarounds exist for this issue:

Option 1: Add an account with a name that comes first alphabetically. Then, turn off the agents for that account using the sql.agent.disabledAgents parameter in clouddriver-local.yml or the equivalent section of your Operator config file. Use regex for the value instead of attempting to create a list manually.
Option 2: In clouddriver-local.yml or the equivalent section of your Operator config file, disable public image caching with the following parameter: aws.defaults.publicImages.enabled: false.

Highlighted updates

This release includes bug fixes and performance improvements.

Spinnaker Community Contributions

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

Detailed updates

Bill Of Materials (BOM)

Here’s the BOM for this version.

Expand

version: 2.23.3
timestamp: "2021-01-06 18:34:22"
services:
    clouddriver:
        commit: 7b48618e
        version: 2.23.28
    deck:
        commit: c12cb26f
        version: 2.23.15
    dinghy:
        commit: 2af1fe54
        version: 2.23.8
    echo:
        commit: 4ee974dd
        version: 2.23.6
    fiat:
        commit: 733f0a48
        version: 2.23.5
    front50:
        commit: "19492652"
        version: 2.23.6
    gate:
        commit: 55345b5a
        version: 2.23.5
    igor:
        commit: 06ff06e0
        version: 2.23.5
    kayenta:
        commit: 602679b2
        version: 2.23.8
    monitoring-daemon:
        version: 2.23.0
    monitoring-third-party:
        version: 2.23.0
    orca:
        commit: 95f678f3
        version: 2.23.12
    rosco:
        commit: c2b498c9
        version: 2.23.10
    terraformer:
        commit: 25d9a96b
        version: 2.23.6
dependencies:
    redis:
        version: 2:2.8.4-2
artifactSources:
    dockerRegistry: docker.io/armory

Armory

Armory Deck - 2.23.14…2.23.15

chore(deps): bump to new OSS 1.23.5 bom (#710)

Armory Front50 - 2.23.6…2.23.6

Terraformer™ - 2.23.5…2.23.6

refactor(git/repo): improve git/repo perf (bp #295) (#296)

Armory Kayenta - 2.23.7…2.23.8

fix(kayenta): force oss version to 1.24.0 (#158)

Armory Orca - 2.23.12…2.23.12

Armory Gate - 2.23.5…2.23.5

Armory Echo - 2.23.6…2.23.6

Dinghy™ - 2.23.8…2.23.8

Armory Fiat - 2.23.5…2.23.5

Armory Clouddriver - 2.23.27…2.23.28

feat(docker): adding ecr utility to get an ecr token (#235) (#237)

Armory Igor - 2.23.5…2.23.5

Armory Rosco - 2.23.10…2.23.10

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 3, 2023: (22c29bf4)