Armory Docs – Release Notes for Armory Products

Continuous-Deployment: Armory Continuous Deployment Release Notes

Mon, 01 Jan 0001 00:00:00 +0000

Minimum Armory Operator version

To install, upgrade, and configure Armory Continuous Deployment (Armory CD), ensure that you are running at least the minimum Operator version for your release:

Armory CD version	Minimum Operator version
2.32.x	1.8.6
2.30.x	1.8.6
2.28.x	1.6.0
2.27.x	1.4.0

LTS releases

Starting with version 2.27.1, Armory CD follows a Long Term Support (LTS) release model with two LTS releases per year. An LTS release contains significant features and changes.

Armory supports the three (3) most recent LTS releases.

During the supported lifetime of an LTS release, Armory ships Feature releases for the LTS.

Feature releases

Starting with version 2.31.0, Armory is introducing a Feature release, which is an additional type of major release that complements an LTS release. Feature releases may contain bug fixes, performance improvements, CVE remediation, and non-breaking features or enhancements placed behind a feature flag.

Feature releases do the following:

Enable customers to test and consume Armory CD and open source Spinnaker features faster
Improve the quality and stability of LTS releases by having changes tested and validated within the Feature releases

Armory releases an LTS version approximately every 6 months, with one or two Feature releases between LTS releases. Feature releases have a shortened support window of 6 months.

Continuous-Deployment: Armory Continuous Deployment PreRelease Release Notes

Mon, 01 Jan 0001 00:00:00 +0000

Continuous-Deployment: Armory Operator Release Notes

Mon, 01 Jan 0001 00:00:00 +0000

Upgrade the Operator using kubectl replace. See Upgrade the Operator for details.

You can find Armory Continuous Deployment releases notes here.

Release Notes

Continuous-Deployment: Testing Methodologies

Mon, 01 Jan 0001 00:00:00 +0000

CI Process

Unit Testing

As part of our CI process, we run unit tests with each PR. We push as much to unit tests as possible, to ensure the service works as expected. Between open source and armory, we run thousands of unit tests with each release.

Integration Testing

As part of the CI process, we also run integration tests, in order to test service to service contracts. This type of testing is great for finding service communication and compatibility issues.

End-to-End Testing

Once both unit and integration tests pass and a new image is created for use, we run end to end tests. End to end testing helps verify workflows and complex, real world interactions.

Release Testing

Manual Testing

After a release candidate is created and has passed all of our automated tests, we perform a series of manual tests.

On Demand Testing

Load testing

We conduct load testing when necessary. For instance, we perform load tests in the following scenarios:

Architectural changes
Encounter a new unit of scale
- For example, how does Armory Continuous Deployment perform as
  - More AWS Accounts are added
  - Number of Cloudwatch metrics increases
  - Increase in Kubernetes namespaces

Tuning

When installing Armory Continuous Deployment in a customer environment, because customer environments are unique, we first have to understand the customer’s units of scale. From there, we install an Armory Continuous Deployment instance based on a few profiles we’ve tested. After Armory Continuous Deployment is installed, we utilize monitoring and metrics in order to tune and scale a Armory Continuous Deployment environment for the customers’ units of scale. See Armory Continuous Deployment Monitoring Metrics