Armory Continuous Deployment Compatibility Matrix

Compatibility matrix overview

This compatibility matrix details what is supported in the Armory Continuous Deployment 2.34.x release. Compatibility is for all minor versions of a major release version. Note that although Spinnaker™ is part of Armory Continuous Deployment, what open source Spinnaker supports and what Armory Continuous Deployment supports is not a one-to-one relationship.

You can find the compatibility matrix for previous Armory Continuous Deployment releases in the docs version for the release you are using:

• Armory Continuous Deployment v2.31 compatibility matrix
• Armory Continuous Deployment v2.30 compatibility matrix
• Armory Continuous Deployment v2.28 compatibility matrix
• Armory Continuous Deployment v2.27 compatibility matrix
• Armory Continuous Deployment v2.26 compatibility matrix

See System Requirements for Armory Continuous Deployment for information about the system requirements you need to install Armory Continuous Deployment.

Legend

Feature status describes what state the feature is in and where you should install it. For more information, see Release Definitions. You can also click on the feature status badge directly.

The feature as a whole is generally available. There may be newer extended functionality that is in a different state.

Beta The feature is in Early Access. For more information about using this feature, contact us.

The feature is in Early Access. For more information about using this feature, contact us.

The feature is an Experiment. For more information about using this feature, contact us.

Enterprise availability

The feature or parts of it are available in open source Spinnaker (OSS).

The feature or parts of it are available only as part of Armory Continuous Deployment for Spinnaker.¹

Versions

All supported versions for the Armory Continuous Deployment version refers to the current minor release and the two previous minor releases. For example, if the current version is 2.21.x, all supported versions include 2.19.x, 2.20.x, and 2.21.x. For third-party software, “all supported versions” refers to actively maintained versions by the provider.

Armory Operator

The Armory Operator and Spinnaker Operator provide you with the ability to install, update, and maintain your clusters via a Kubernetes operator.

Note that newer versions of the Armory Operator drop support for older Kubernetes versions. The following table outlines the supported combinations of Kubernetes, the Operator, and Armory Continuous Deployment:

• Armory Continuous Deployment
• Open Source Spinnaker

Consult the Manage Operator guide for how to upgrade your Operator version.

Application metrics for Canary Analysis

Application metrics can be ingested by Kayenta to perform Canary Analysis or Automated Canary Analysis (ACA). For information about how to enable Canary Analysis, see Configure Automated Canary Deployments in Spinnaker.

The following table lists supported app metric providers:

Artifacts

Artifacts are deployable resources.

The following table lists the supported artifact stores:

As code solutions

Pipelines-as-Code

Armory’s Pipelines-as-Code feature provides a way to specify pipeline definitions in source code repos such as GitHub and BitBucket.

The Pipelines-as-Code has two components: 1) a Spinnaker plugin; and 2) a service called Dinghy, which keeps the Spinnaker pipeline in sync with what you define in a dinghyfile in your repo. You can also make a pipeline by composing other pipelines, stages, or tasks and templating certain values.

GitHub is in the process of replacing master as the name of the default base branch. Newly created repos use main. As this transition happens, confirm what branch your repo is using as its base branch and explicitly refer to that branch when configuring Armory features such as Pipelines-as-Code. For more information, see GitHub’s Renaming information.

Templating languages

To create a dinghyfile, you can use one of the following templating languages:

• HashiCorp Configuration Language (HCL)
• JSON
• YAML

ARM CLI

The ARM CLI is a tool to render dinghyfiles and modules. Use it to help develop and validate your pipelines locally.

You can find the latest version on Docker Hub.

Terraform Integration

Use Terraform within your pipelines to create your infrastructure as part of your software delivery pipeline. Terraform Integration is a feature in Armory CD and a plugin for Spinnaker. For more information see the Terrafrom Integration docs.

Supported Terraform versions

Not all patch versions are included for each release. Although other Terraform versions may be usable with Spinnaker/Armory CD and Terraform Integration, Armory only supports the versions listed here.

Features

The following table lists the Terraform Integration features and their supported versions:

Support is limited to configuring Terraform Integration and using the stage within Armory Continuous Deployment. Armory’s Customer Care team does not troubleshoot Terraform script issues or infrastructure creation using Terraform. If you have questions, contact your assigned Technical Account Manager and/or Account Executive. Alternatively, you can reach our Customer Care team by visiting the Armory Support Portal to submit a case.

Authentication

The following table lists the supported authentication protocols:

Authorization

The following table lists the supported authorization methods:

Baking machine images

The following table lists the supported image bakeries:

Baking Kubernetes manifests

The following table lists the supported manifest templating engines:

Build systems

The following table lists the supported CI systems:

Custom stages

Armory Continuous Deployment includes custom stages that you can use to extend the capabilities of Armory Continuous Deployment. Some of these stages are available out of the box while others are available as plugins to Armory Continuous Deployment.

Stage	Armory Continuous Deployment Version	Notes
Evaluate Artifacts	2.24.0 and later	Available as a plugin

Deployment targets

Armory Continuous Deployment supports various deployment targets.

Here’s a great chart by Google to help you understand how the different deployment targets are categorized.

Compute as a Service

Container as a Service Platforms

These are manifest-based providers. Armory Continuous Deployment applies the manifest and leaves the rollout logic to the platform itself.

Platform as a Service

Serverless

You write the function and use Armory Continuous Deployment to manage the rollout of iterative versions. These are usually hosted by Cloud Providers.

Dynamic accounts

Dynamic accounts (external account configurations) allow you to manage account configuration outside of Spinnaker, including secrets.

Note that Armory Continuous Deployment does not support using dynamic account configuration with Spring Cloud Config Server.

Backend provider

The following table lists the supported backends:

Supported Spinnaker services

The following table lists the services that support dynamic accounts:

Notifications

The following table lists the supported notification systems:

Observability

The following table lists the supported observability providers:

Pipeline triggers

The following table lists the supported pipeline triggers:

Secret stores

The following table lists the supported secret stores for referencing secrets in config files securely: