v2.24 Armory Platform Compatibility Matrix
This page describes the features and capabilities that Armory supports. Note that although Spinnaker™ is part of the Armory Platform, what Open Source Spinnaker supports and what Armory supports is not a one-to-one relationship.
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.
The feature is in Early Access.
The feature is an Experiment.
Enterprise availablility
The feature or parts of it are available in Open Source Spinnaker.
The feature or parts of it are available only as part of the Armory Platform.
Versions
All supported versions for the Armory 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.
Application metrics for Canary Analysis
Application metrics can be ingested by Kayenta to perform Canary Analysis or Automated Canary Analysis (ACA). The following table lists supported app metric providers:
| Provider | Version | ACA | Armory | Note |
|---|---|---|---|---|
| AWS Cloudwatch | All supported versions | Yes | 2.23.1 or later | |
| 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 (Open Source) | All supported versions | Yes | All supported versions | Authentication using a bearer token is supported. |
| SignalFx | All supported versions | Yes | All supported versions | |
| Stackdriver | All supported versions | Yes | All supported versions |
Artifacts
Artifacts are deployable resources.
Stores
The following table lists the supported artifact stores:
| Provider | Armory | Notes |
|---|---|---|
| Bitbucket | All supported versions | |
| GitHub | All supported versions | |
| GitLab | 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 | |
| Oracle Object | All supported versions | |
| S3 | All supported versions |
Types
The following table lists the supported artifact types:
| Type | Armory | Notes |
|---|---|---|
| Bitbucket file | All supported versions | |
| Docker Image | All supported versions | Can be hosted on DockerHub, GCR, ECR, etc |
| Embedded Base64 | All supported versions | |
| GCS Object | All supported versions | |
| Git Repo | All supported versions | |
| GitHub file | All supported versions | |
| GitLab file | All supported versions | |
| HTTP file | All supported versions | |
| Kubernetes object | All supported versions | |
| Maven artifact | All supported versions | |
| Oracle Object | All supported versions | |
| S3 object | 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.
Supported version control systems
The following table lists the supported version control systems:
| Feature | Version | Armory version | Notes |
|---|---|---|---|
| BitBucket Cloud | All supported versions | ||
| BitBucket Server | Previous two major versions | All supported versions | |
| GitHub | All supported versions | Hosted or cloud | |
| GitLab | All supported versions |
Features
The following table lists specific features for Pipelines as Code and their supported versions:
| Feature | Armory | Notes |
|---|---|---|
| Modules | All supported versions | Templatize and re-use pipeline snippets across applications and teams |
| Slack notifications | All supported versions | |
| Fiat service account integration | All supported versions | |
| Webhook secret validation | 2.20 or later | |
| Local modules for development | 2.20 or later | |
| Pull Request Validation | 2.21 or later |
Pipelines as CRD
This feature is deprecated. For more information, see [PaCRD Deprecation]/docs/feature-status/deprecations/pacrd-deprecation/.
PaCRD gives you the ability to manage your pipelines as Kubernetes custom resources.
The following table lists the PaCRD features and their supported versions:
| Feature | Armory | Notes |
|---|---|---|
| Create, modify, and delete pipeline manifests | All supported versions | Working within the same cluster Spinnaker is installed in. |
| Create, modify, and delete application manifests | All supported versions | Working within the same cluster Spinnaker is installed in. |
| Define all stages supported by Spinnaker and Armory | PaCRD version 0.10.x and later | Validation support does not exist for all stages. |
Terraform Integration
The Terraform Integration gives you the ability to use Terraform within your Spinnaker pipelines to create your infrastructure as part of your software delivery pipeline.
Supported Terraform versions
The following table lists the supported Terraform versions:
| Terraform Versions | Armory | Note |
|---|---|---|
| 0.11.10 - 0.11.14 | All supported versions | |
| 0.12.0 - 0.12.24 | All supported versions |
Features
The following table lists the Terraform Integration features and their supported versions:
| Feature | Armory | Notes |
|---|---|---|
| Base Terraform Integration | All supported versions | |
| Named Profiles with authorization | 2.20 or later |
Authentication
The following table lists the supported authentication protocols:
| Identity provider | Armory | Note |
|---|---|---|
| None | All supported versions | We highly recommend having Spinnaker only accessible through a VPN if this is turned on. |
| Basic | All supported versions | Only one username/password can be configured at a time. |
| 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 | |
| IAP | All supported versions | |
| x509 | All supported versions |
Authorization
The following table lists the supported authorization methods:
| Provider | Armory | Note |
|---|---|---|
| None | All supported versions | We highly recommend having Spinnaker 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 | |
| SAML | All supported versions |
Baking Images
The following table lists the supported image bakeries:
| Provider | Armory | Notes |
|---|---|---|
| AWS | All supported versions | |
| GCE | All supported versions | |
| OCI | All supported versions | |
| Packer | All supported versions | Spinnaker includes Packer. |
Browsers
Spinnaker’s UI (Deck) works with most modern browsers.
Build systems
The following table lists the supported CI systems:
| Provider | Version | Armory | Note |
|---|---|---|---|
| AWS CodeBuild | n/a | 2.19.x or later | |
| GitHub Actions | n/a | All supported versions | Webhook integration |
| Google Cloud Build | n/a | ||
| Jenkins | All supported versions | All supported versions | |
| Travis | All supported versions | All supported versions | |
| Wercker | All supported versions | All supported versions |
Deployment targets
Armory 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 Versions | Notes |
|---|---|---|---|
| Amazon AWS EC2 |
|
All supported versions | AWS Public Cloud only. Armory does not support GovCloud. |
| Google Cloud Compute Engine |
|
All supported versions |
Container as a Service Platforms
These are providers that are manifest based, so Armory applies the manifest and leaves the rollout logic to the platform itself.
| Provider | Supported Versions | Armory Versions | Notes |
|---|---|---|---|
| Kubernetes | All versions | All supported versions | |
| Amazon AWS EKS | All versions | All supported versions | AWS Public Cloud only. Armory does not support GovCloud. |
| Google GKE | All versions | All supported versions | |
| VMware/Pivotal PKS | All versions | All supported versions |
| Provider | Deployment strategies | Armory Versions | Notes |
|---|---|---|---|
| Amazon AWS ECS |
|
All supported versions | AWS Public Cloud only. Armory does not support GovCloud. |
Platform as a Service
| Provider | Supported Versions | Deployment strategies | Armory Versions | 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 to manage the rollout of iterative versions. These are usually hosted by Cloud Providers.
| Provider | Deployment strategies | Armory Versions | Notes |
|---|---|---|---|
| Amazon AWS Lambda |
|
All supported versions | AWS Public Cloud only. Armory does not support GovCloud. |
Dynamic accounts
Dynamic accounts (external account configurations) for Spinnaker allow you to manage account configuration outside of Spinnaker, including secrets.
Note that Armory does not support using dynamic account configuration with Spring Cloud Config Server.
Backend provider
The following table lists the supported backends:
| Provider | Version | Armory | 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 |
External storage
Spinnaker requires an external storage provider for persisting app settings and pipelines. The following table lists the supported storage solutions:
| Provider | Armory | Notes |
|---|---|---|
| Azure Storage | All supported versions | |
| Google Cloud Storage | All supported versions | |
| Minio | All supported versions | |
| S3 | All supported versions | |
| Oracle Object Storage | All supported versions |
Manifest templating
The following table lists the supported manifest templating engines:
| Provider | Armory | Notes |
|---|---|---|
| Helm 2 | All supported versions | |
| Helm 3 | 2.19.x or later | |
| Kustomize | All supported versions | Kustomize version installed is 3.8.1 |
Notifications
The following table lists the supported notification systems:
| Provider | Armory | Notes |
|---|---|---|
| BearyChat | All supported versions | |
| All supported versions | ||
| GitHub | All supported versions | |
| GoogleChat | All supported versions | |
| Jira | All supported versions | |
| MS Teams | 2.23.2 or later | |
| Slack | All supported versions | |
| PagerDuty | All supported versions | |
| Twilio | All supported versions |
Observability
The following table lists the supported observabilty providers:
| Provider | Version | Armory | Note |
|---|---|---|---|
| New Relic | All supported versions | All supported versions | |
| Prometheus (Open Source) | All supported versions | All supported versions | Use Grafana for dashboards. |
Persistent storage
Depending on the service, Spinnaker can use either Redis or MySQL as the backing store. The following table lists the supported database and the Spinnaker service:
| Database | DB version | Armory | Spinnaker services | Note |
|---|---|---|---|---|
| Redis | All supported versions | All supported versions | All Spinnaker services that require a backing store | The DB versions refer to external Redis instances. By default, Spinnaker deploys Redis internally to support its services. |
| MySQL | MySQL 5.7 (or Aurora) | All supported versions | Clouddriver, Front50, Orca |
Armory recommends using MySQL as the backing store when possible for production instances of Spinnaker. For other services, use an external Redis instance for production instances of Spinnaker.
Pipeline triggers
The following table lists the supported pipeline triggers:
| Provider | Armory | Notes |
|---|---|---|
| Artifactory | All supported versions | |
| AWS CodeBuild | All supported versions | |
| AWS Pub/Sub | All supported versions | |
| Cron | All supported versions | |
| Docker | All supported versions | |
| Git | All supported versions | |
| GitHub Webhook | All supported versions | |
| Google Cloud Build | All supported versions | |
| Google Pub/Sub | All supported versions | |
| Jenkins Job | All supported versions | |
| Webhook | All supported versions | |
| Manual | All supported versions | |
| TravisCI Job | All supported versions | |
| Wercker | All supported versions | |
| Quay | All supported versions | |
| Nexus | All supported versions | |
| GitLab | All supported versions |
Policy Engine
The Policy Engine gives you the ability to ensure any Spinnaker pipeline meets certain requirements you specify.
OPA requirements
The Policy Engine requires an Open Policy Agent server. This can be deployed in the same cluster as Spinnaker 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 specify the OPA server URL in the Armory configs, include v1 in the URL: http://<your-opa-server>:<port>/v1. |
Supported validations
| Validation | Armory | 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 | Notes |
|---|---|---|
| AWS Secrets Manager | All supported versions | |
| Encrypted GCS Bucket | All supported versions | |
| Encrypted S3 Bucket | All supported versions | |
| Kubernetes secrets | All supported versions | Spinnaker Operator based deployments |
| Vault | All supported versions | Armory only |
Spinnaker Operator
Spinnaker Operator and Armory Operator provide Spinnaker users with the ability to install, update, and maintain their clusters via a Kubernetes operator.
| Feature | Version | Armory 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. |
Feedback
Was this page helpful?
Thank you for letting us know!
Sorry to hear that. Please tell us how we can improve.
Last modified August 3, 2021: (a9ef9bc)