Armory Enterprise Compatibility Matrix
Compatibility matrix overview
This compatibility matrix details what is supported in the Armory Enterprise 2.28.0 release. Compatibility is for all minor versions of a major release version. Note that although Spinnaker™ is part of Armory Enterprise, what open source Spinnaker supports and what Armory Enterprise supports is not a one-to-one relationship.
You can find the compatibility matrix for previous Armory Enterprise releases in the docs version for the release you are using:
- Armory Enterprise v2.27 compatibility matrix
- Armory Enterprise v2.26 compatibility matrix
- Armory Enterprise v2.25 compatibility matrix
See System Requirements for Armory Enterprise for information about the system requirements you need to install Armory Enterprise.
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 Enterprise for Spinnaker.1
Versions
All supported versions for the Armory Enterprise 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 Agent
| Armory CD (Spinnaker) Version | Armory Agent Plugin Version | Armory Agent Version |
|---|---|---|
| 2.26.x (1.26.x) | 0.9.73 | 1.0.27 |
| 2.27.x (1.27.x) | 0.10.58 | 1.0.27 |
| 2.28.x (1.28.x) | 0.11.20 | 1.0.27 |
Your Clouddriver service must use a MySQL-compatible database. See the Configure Clouddriver to use a SQL Database guide for instructions.
Database compatibility:
| MySQL | PostgreSQL |
|---|---|
| 5.7; AWS Aurora | 10+ |
For a full list of previous releases, see this page.
Armory Operator
The Armory Operator and Spinnaker Operator provide you with the ability to install, update, and maintain your clusters via a Kubernetes operator.
| Feature | Version | Armory Enterprise Version | Notes |
|---|---|---|---|
| Install, update, and maintain Spinnaker clusters | All supported versions | All supported versions | |
| Automatically determine Deck/Gate URL configuration if Ingress objects are defined | 1.1.0 or later | 1.1.1 or later | Ingress objects must be defined in the same namespace where Spinnaker lives. |
| Support definition of all Halyard configuration options | All supported versions | All supported versions | |
| In cluster mode, validate configuration before apply | All supported versions | All supported versions | Does not work when installed in “basic” mode. Does not guarantee a valid configuration, but does check for most common misconfigurations. |
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 Enterprise:
| Kubernetes Version | Armory Operator Version | Armory Enterprise Version |
|---|---|---|
| < 1.21 | <= 1.6.x | <= 2.28.0 |
| >= 1.21 | >= 1.7.x | All Supported Enterprise Versions |
For guidance on upgrading the Operator, consult the Manage Operator guide.
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:
| Provider | Version | ACA | Armory Enterprise Version | Note |
|---|---|---|---|---|
| AWS Cloudwatch | All supported versions | Yes | 2.23.1 or later | |
| Datadog | All supported versions | Yes | 2.26.0 or later | Beta |
| Dynatrace | All supported versions | Yes | 2.23.0 or later | |
| Graphite | All supported versions | Yes | All supported versions | |
| New Relic | All supported versions | Yes | All supported versions | |
| Prometheus | All supported versions | Yes | All supported versions | Authentication using a bearer token is supported. Armory supports offerings that are proprietary versions of Prometheus, such as Cortex, to the extent that the offering overlaps with open source Prometheus. That is, Armory guarantees functionality that is compatible with open source Prometheus. Compatibility between open source Prometheus and the proprietary version is the responsibility of that vendor, not Armory. |
| SignalFx | All supported versions | Yes | All supported versions | |
| Stackdriver | All supported versions | Yes | All supported versions |
Artifacts
Artifacts are deployable resources.
The following table lists the supported artifact stores:
| Provider | Armory Enterprise Version | Notes |
|---|---|---|
| Bitbucket | All supported versions | |
| Container registries | All supported versions | Docker Hub, ECR, and GCR |
| GitHub | All supported versions | |
| Git Repo | All supported versions | GitHub or Bitbucket. Supports using the entire repo as an artifact. |
| Google Cloud Storage | All supported versions | |
| HTTP | All supported versions | |
| Maven | All supported versions | |
| S3 | All supported versions |
As code solutions
Pipelines as Code
Pipelines as Code gives you the ability to manage your pipelines and their templates in source control by creating and maintaining dinghyfiles that contain text representations of pipelines. These files are then ingested by Armory Enterprise to generate pipelines that your app devs can use to deploy their apps.
Templating languages
To create dinghyfiles, you can use one of the following templating languages:
- HashiCorp Configuration Language (HCL)
- JSON
- YAML
Version control systems
The following table lists the supported version control systems:
| Feature | Version | Armory Enterprise Version | Notes |
|---|---|---|---|
| BitBucket Cloud | All supported versions | ||
| BitBucket Server | 4.x - 6.x | All supported versions | BitBucket Server 7.x is not officially supported due to changes in webhook handling and may not behave as expected. |
| GitHub | All supported versions | Hosted or cloud |
Features
The following table lists specific features for Pipelines as Code and their supported versions:
| Feature | Armory Enterprise Version | Notes |
|---|---|---|
| Fiat service account integration | All supported versions | |
| GitHub status notifications | All supported versions | |
| Local modules for development | All supported versions | |
| Modules | All supported versions | Templatize and re-use pipeline snippets across applications and teams |
| Pull Request Validation | 2.21 or later | |
| Slack notifications | All supported versions | |
| Webhook secret validation | All supported versions |
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. For more information see Enable the Terraform Integration Stage in Armory Enterprise and Use the Terraform Integration Stage in Armory Enterprise.
Supported Terraform versions
| CDSH Version | Terraform Supported Versions | Notes |
|---|---|---|
| 2.26 | 0.11, 0.12, 0.13, 0.14, 0.15, 1.0 | |
| 2.27 | 0.11, 0.12, 0.13, 0.14, 0.15, 1.0, 1.1, 1.2 | |
| 2.28 | 0.12, 0.13, 0.14, 0.15, 1.0, 1.1, 1.2 | Version 0.12 was not available in 2.28 but is supported as of release 2.28.1. |
Note
Not all patch versions are included for each release. Although other Terraform versions may be usable with Armory Enterprise and the Terraform Integration, only the versions listed here are supported.Features
The following table lists the Terraform Integration features and their supported versions:
| Feature | Armory Enterprise Version | Notes |
|---|---|---|
| Base Terraform Integration | All supported versions | |
| Named Profiles with authorization | All supported versions |
Support is limited to configuring Terraform Integration and using the stage within Armory Enterprise. 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:
| Identity provider | Armory Enterprise Version | Note |
|---|---|---|
| None | All supported versions | Armory recommends having Armory Enterprise only accessible through a VPN if this is turned on. |
| SAML | All supported versions | |
| OAuth 2.0/OIDC | All supported versions | You can use any OAuth 2.0 provider such as Auth0, Azure, GitHub, Google, Okta, OneLogin, or Oracle Cloud. |
| LDAP/Active Directory | All supported versions | |
| x509 | All supported versions |
Authorization
The following table lists the supported authorization methods:
| Provider | Armory Enterprise Version | Note |
|---|---|---|
| None | All supported versions | Armory recommends having Armory Enterprise only accessible through a VPN if this is turned on. |
| GitHub Teams | All supported versions | Roles from GitHub are mapped to the Teams under a specific GitHub organization. |
| Google Groups | All supported versions | |
| LDAP/Active Directory | All supported versions | |
| OAuth 2.0/OIDC | All supported versions | Requires the provider to include groups in claims or be a supported third party integration. |
| SAML | All supported versions |
Baking machine images
The following table lists the supported image bakeries:
| Provider | Armory Enterprise Version | Notes |
|---|---|---|
| AWS | All supported versions | |
| GCE | All supported versions | |
| Packer | All supported versions | The following lists the included Packer versions:
|
Baking Kubernetes manifests
The following table lists the supported manifest templating engines:
| Provider | Armory Enterprise Version | Notes |
|---|---|---|
| Helm 2 | All supported versions | |
| Helm 3 | 2.19.x or later | |
| Kustomize | All supported versions | Kustomize version installed is 3.8.1 |
Build systems
The following table lists the supported CI systems:
| Provider | Version | Armory Enterprise Version | Note |
|---|---|---|---|
| GitHub Actions | n/a | All supported versions | Webhook integration |
| Jenkins | All supported versions | All supported versions |
Custom stages
Armory Enterprise includes custom stages that you can use to extend the capabilities of Armory Enterprise. Some of these stages are available out of the box while others are available as plugins to Armory Enterprise.
| Stage | Armory Enterprise Version | Notes |
|---|---|---|
| Evaluate Artifacts | 2.24.0 and later | Available as a plugin |
Deployment targets
Armory Enterprise 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
| Provider | Deployment strategies | Armory Enterprise Version | Notes |
|---|---|---|---|
| Amazon AWS EC2 |
|
All supported versions | AWS Public Cloud only. Armory does not support GovCloud. |
Container as a Service Platforms
These are manifest-based providers. Armory Enterprise applies the manifest and leaves the rollout logic to the platform itself.
| Provider | Version | Armory Enterprise Version | Notes |
|---|---|---|---|
| Kubernetes | 1.16 or later | All supported versions | |
| Amazon AWS EKS | All versions | All supported versions | |
| Google GKE | All versions | All supported versions |
| Provider | Deployment strategies | Armory Enterprise Version | Notes |
|---|---|---|---|
| Amazon AWS ECS |
|
All supported versions | AWS Public Cloud only. Armory does not support GovCloud. |
Platform as a Service
| Provider | Version | Deployment strategies | Armory Enterprise Version | Notes |
|---|---|---|---|---|
| Google Cloud App Engine |
|
All supported versions | ||
| Cloud Foundry | CC API Version: 2.103.0+ and 3.38.0+ |
|
All supported versions | Support for the Cloud Foundry provider is based on your license agreement with Armory. If you have questions, contact your assigned Technical Account Manager and/or Account Executive. Alternatively, you can reach our Customer Care team at support@armory.io or visit the Help Center to submit a case. |
Serverless
You write the function and use Armory Enterprise to manage the rollout of iterative versions. These are usually hosted by Cloud Providers.
| Provider | Deployment strategies | Armory Enterprise Version | Notes |
|---|---|---|---|
| Amazon AWS Lambda |
|
All supported versions | AWS Public Cloud only. Armory does not support GovCloud. |
Dynamic accounts
Dynamic accounts (external account configurations) allow you to manage account configuration outside of Spinnaker, including secrets.
Note that Armory Enterprise does not support using dynamic account configuration with Spring Cloud Config Server.
Backend provider
The following table lists the supported backends:
| Provider | Version | Armory Enterprise Version | Notes |
|---|---|---|---|
| Git | All supported versions | All supported versions | |
| S3 | n/a | All supported versions | |
| Vault | All supported versions | All supported versions |
Supported Spinnaker services
The following table lists the services that support dynamic accounts:
| Service | Account types | Note |
|---|---|---|
| Clouddriver | Cloud provider, artifact | Automatic configuration refreshing is supported for Cloud Foundry and Kubernetes cloud provider accounts only. |
| Echo | Pub/Sub | |
| Igor | CI systems, version control |
Notifications
The following table lists the supported notification systems:
| Provider | Armory Enterprise Version | Notes |
|---|---|---|
| All supported versions | ||
| GitHub | All supported versions | |
| MS Teams | 2.23.2 or later | |
| Slack | All supported versions | |
| PagerDuty | All supported versions |
Observability
The following table lists the supported observability providers:
| Provider | Version | Armory Enterprise Version | Note |
|---|---|---|---|
| New Relic | All supported versions | All supported versions | |
| Prometheus | All supported versions | All supported versions | Use Grafana for dashboards. Armory supports offerings that are proprietary versions of Prometheus, such as Cortex, to the extent that the offering overlaps with open source Prometheus. That is, Armory guarantees functionality that is compatible with open source Prometheus. Compatibility between open source Prometheus and the proprietary version is the responsibility of that vendor, not Armory. |
Pipeline triggers
The following table lists the supported pipeline triggers:
| Provider | Armory Enterprise Version | Notes |
|---|---|---|
| AWS Pub/Sub | All supported versions | |
| Cron | All supported versions | |
| Docker | All supported versions | Docker Registry API v2 required |
| Git | All supported versions | |
| GitHub Webhook | All supported versions | |
| Google Pub/Sub | All supported versions | |
| Jenkins Job | All supported versions | |
| Manual | All supported versions | |
| Webhook | All supported versions |
Policy Engine
The Policy Engine gives you the ability to ensure any pipeline meets certain requirements that you specify.
OPA requirements
The Policy Engine requires an Open Policy Agent server. This can be deployed in the same cluster as Armory Enterprise or in an external cluster.
The following table lists the requirements:
| Requirement | Version | Note |
|---|---|---|
| OPA Server | 0.12.x or later | Specifically, the v1 API must be available. When you specify the OPA server URL in the Armory Enterprise configs, include v1 in the URL: http://<your-opa-server>:<port>/v1. |
Supported validations
| Validation | Armory Enterprise Version | Note |
|---|---|---|
| Save time validation | All supported versions | If no policies are set, you cannot save any pipelines until you set any policy or turn off save time validation. |
| Runtime validation | All supported versions | If no policies are set, no policy enforcement occurs and pipelines run as they do normally. |
Secret stores
Note
This section applies to secrets in configuration files, not application secrets.The following table lists the supported secret stores for referencing secrets in config files securely:
| Provider | Armory Enterprise Version | Notes |
|---|---|---|
| AWS Secrets Manager | All supported versions | |
| Encrypted GCS Bucket | All supported versions | |
| Encrypted S3 Bucket | All supported versions | |
| Kubernetes secrets | All supported versions | Armory Operator based deployments |
| Vault | All supported versions | Proprietary feature |
-
Some of Armory Enterprise’s features are proprietary and require a license for use. For more information, see the Terms of Service and Terms & Conditions. ↩︎
Feedback
Was this page helpful?
Thank you for letting us know!
Sorry to hear that. Please tell us how we can improve.
Last modified October 14, 2022: (02914b60)