Armory Scale Agent Architecture
Scale Agent plugin for Clouddriver
The Scale Agent plugin runs inside Clouddriver and manages migrated accounts and accounts created specifically for Scale Agent management. The plugin does not engage in outbound communication. Through Clouddriver, the plugin exposes an internally-accessible REST API that you can use to dynamically migrate and manage Kubernetes accounts.
Scale Agent service for Kubernetes
You Scale Agent service monitors your Kubernetes clusters and sends information to the Scale Agent plugin running inside Clouddriver.
The Agent service sends the following information about the cluster it is watching to the Clouddriver plugin:
- Account properties as configured in
- Kubernetes API server host, certificate fingerprint, and version.
- All the Kubernetes objects it is configured to watch and has permissions to access. You can ignore certain Kubernetes kinds (
kubernetes.accounts.omitKinds) or configure specific kinds to watch (
The Agent service always scrubs data from
Secretin memory before it is sent and even before that data makes it onto the Armory Scale Agent’s memory heap.
Kubernetes permissions for the service
The Agent service should have
ClusterRole authorization if you need to deploy pods across your cluster. If you only deploy pods only to a single namespace, the service needs
See Kubernetes Permissions for the Armory Scale Agent for detailed information.
Communication and networking
Communication from the Scale 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 Armory Agent service and Clouddriver plugin.
Except for a local health check, the Agent service makes outbound calls only to the Clouddriver plugin over a single gPRC connection. The connection can be over TLS or mTLS. You can terminate TLS:
- On Clouddriver: in the case of running the Armory Scale Agent in Spinnaker Service mode or if declaring
spin-clouddriver-grpcas a network load balancer.
- On a gRPC proxy that directs request to the
The Clouddriver plugin uses the bidirectional communication channel to receive changes from Kubernetes accounts as well as send operations to the Armory Scale Agent service.
See the Armory Scale Agent Communication With Clouddriver Instances in Kubernetes page for detailed information.
Since the Armory Scale Agent service does outbound calls only, you can have Agent services running on-premises or in public clouds such as AWS, GCP, Azure, Oracle, or Alibaba.
What the Scale Agent service can do in the target cluster is limited by what it is running as:
serviceAccountin Agent mode
kubeconfigsetup for infrastructure or Spinnaker service mode
Communications are secured with TLS and optionally mTLS.
- Kubernetes Permissions for the Armory Scale Agent
- Armory Scale Agent Communication With Clouddriver Instances in Kubernetes
Was this page helpful?
Thank you for letting us know!
Sorry to hear that. Please tell us how we can improve.
Last modified March 3, 2023: (2d06908)