Armory Agent for Kubernetes Installation
This installation guide is designed for installing the Agent in a test environment. It does not include mTLS configuration, so the Agent service and plugin do not communicate securely.
Before you begin
- You deployed Armory Enterprise using the Armory Operator and Kustomize patches.
- You have configured Clouddriver to use MySQL or PostgreSQL. See the Configure Clouddriver to use a SQL Database guide for instructions. The Agent plugin uses the SQL database to store cache data.
- You have a running Redis instance. The Agent plugin uses Redis to coordinate between Clouddriver replicas. Note: you need Redis even if you only have one Clouddriver instance.
- You have read the Armory Agent overview.
- If you are running multiple Clouddriver instances, you have a running Redis instance. The Agent uses Redis to coordinate between Clouddriver replicas.
- You have an additional Kubernetes cluster to serve as your deployment target cluster.
Communication from the Agent service to the Clouddriver plugin occurs over gRPC port 9091. Communication between the service and the plugin must be
http/1.1 is not compatible and causes communication issues between the Agent service and Clouddriver plugin.
|Armory Enterprise (Spinnaker) Version||Armory Agent Plugin Version||Armory Agent Version|
Your Clouddriver service must use a MySQL-compatible database. See the Configure Clouddriver to use a SQL Database guide for instructions.
|5.7; AWS Aurora||10+|
In this guide, you deploy the Agent service to your target cluster.
Install the Clouddriver plugin. You do this in the cluster where you are running Armory Enterprise.
- Create the plugin manifest as a Kustomize patch.
- Create a LoadBalancer service Kustomize patch to expose the plugin on gRPC port
- Apply the manifests.
Install the Agent service using a Helm chart or using
Was this page helpful?
Thank you for letting us know!
Sorry to hear that. Please tell us how we can improve.
Last modified December 10, 2021: (556c295)