Options for deploying Armory Enterprise in an environment that is isolated from the internet.
You are viewing version 2.26 of the documentation, which is no longer maintained. For up-to-date documentation, see the latest version.
Guides for Installing Armory Enterprise for Spinnaker
Once installed, Armory Enterprise can deploy to supported providers through Clouddriver regardless of where it is installed.
See Install Armory Enterprise for Spinnaker in Air-Gapped Environments for additional steps you have to take if you have an air-gapped environment.
Use the Armory Operator from the AWS Container Marketplace to deploy Armory Enterprise for Spinnaker in your Amazon Kubernetes (EKS) cluster.
Use Armory-extended Halyard to deploy Armory Enterprise in an AWS Kubernetes cluster or in an on-prem Kubernetes cluster with access to Amazon Secure Storage Service (S3).
Use the Armory Operator to deploy Armory Enterprise for Spinnaker in your Google Kubernetes Engine (GKE) cluster.
Configure Armory-extended Halyard profiles and storage.
Update or rollback your Armory Enterprise for Spinnaker version deployed with Armory-extended Halyard.
Upgrade your open source Spinnaker deployment to Armory Enterprise for Spinnaker using Armory-extended Halyard.
This section contains guides that show you how to configure AWS for Spinnaker and deploy an application from Spinnaker to AWS.
Use the Armory Operator to deploy Spinnaker or Armory Enterprise in a Lightweight Kubernetes (K3s) instance running on an AWS EC2 virtual machine. This environment is for proofs of concept and development.
Was this page helpful?
Thank you for letting us know!
Sorry to hear that. Please tell us how we can improve.
Last modified September 10, 2021: (28d5cc2)