Armory Continuous Deployment
docs.armory.io
- Windows
- macOS
- Linux
- Web
- Self-hosted
6.8 Club score Visit docs.armory.io
Plans
Every plan and priceArmory Continuous Deployment
—
Pricing on request
What the maker publishes
- Authentication
- Supported authentication methods include SAML, OAuth 2.0/OIDC, LDAP/Active Directory, and x509. source
- Authorization
- Supported authorization options include GitHub Teams, Google Groups, LDAP/Active Directory, OAuth 2.0/OIDC, and SAML. source
- Deployment strategies
- The compatibility matrix lists strategies including canary, blue-green, rolling, and custom pipelines for supported targets. source
- Deployment targets
- The compatibility matrix includes AWS EC2, AWS ECS, Kubernetes, Amazon EKS, Google GKE, Cloud Foundry, Google App Engine, and AWS Lambda. source
- Infrastructure provisioning
- The Terraform Integration plugin enables provisioning infrastructure as part of Spinnaker and Armory CD pipelines. source
- Infrastructure requirements
- Armory CD runs on a certified Kubernetes cluster; the requirements page lists Kubernetes versions 1.20 through 1.25 and says production installations need external storage. source
- Installation options
- The installation guide describes a Minnaker environment on macOS, Linux, or Windows, as well as Kubernetes-based installation methods. source
- Notifications and monitoring
- The compatibility matrix lists Slack, email, GitHub, Microsoft Teams, PagerDuty, New Relic, Prometheus, and Datadog integrations. source
- Pipeline integrations
- Armory Pipelines-as-Code supports managing pipeline definitions as code in GitHub, Bitbucket, or GitLab. source
- Product
- Armory Continuous Deployment is an enterprise distribution of Spinnaker that runs in a Kubernetes cluster and extends it with essential and optional premium plugins. source
- Purpose
- Spinnaker provides continuous delivery and deployment using configurable pipelines made of deployment stages. source
- Secret management
- The compatibility matrix lists AWS Secrets Manager, encrypted GCS and S3 buckets, Kubernetes secrets, and Vault as secret stores for configuration values. source
- Security guidance
- Armory recommends using a secret store for sensitive configuration values and configuring authentication and authorization. source
- Support limitation
- Armory states that support for Terraform Integration covers configuring it and using its pipeline stage, but not troubleshooting Terraform scripts or infrastructure creation. source
Checked against the maker's pages on 30 Sept 2026.