This guide explains how to deploy the Breeze Agent in a Kubernetes cluster.
How it works
The container runs a lightweight daemon that launches the Breeze Agent every 15 minutes.
Create the Docker image
-
Download the Breeze Agent installer and extract it to the current directory:
wget breeze-agent.example.version.0.x86_64.linux.tgz tar xvzf breeze-agent.example.version.0.x86_64.linux.tgz -
Build the image:
-
General build:
docker build -t registry.example.com/breeze-agent:redacted -f Dockerfile . -
AKS build:
docker build -t registry.example.com/breeze-agent:redacted -f Dockerfile.aks .
-
-
Push the image to your private registry:
docker push registry.example.com/breeze-agent:redactedWHERE replace
registry.example.com/breeze-agent:<tag>with your actual registry hostname and desired image tag.
Required RBAC
The Breeze Agent requires specific Kubernetes permissions. Deploy the RBAC manifest:
kubectl apply -f cloudaware-rbac.yaml
Deploy the Breeze Agent
EKS
Requirements
Make sure the following AWS Instance Metadata Service (IMDS) endpoints are accessible from the node:
-
latest/api/token -
latest/dynamic/instance-identity/document -
latest/meta-data/services/partition -
latest/meta-data/placement/region
Also ensure that the node group IAM role includes the ec2:DescribeTags permission (or that an attached policy provides this permission).
Deployment
-
Replace the image placeholder in the
breeze-agent-eks.yamlmanifest with your image path. -
Apply the manifest:
kubectl create -f breeze-agent-eks.yaml
If metadata access is restricted, use the metadata-disabled version – breeze-agent-eks-wo-metadata.yaml:
kubectl create -f breeze-agent-eks-wo-metadata.yaml
WHERE replace the <EKS_CLUSTER_ARN> placeholder with the actual cluster ARN.
AKS
Requirements
Configure AKS-ACR integration.
Deployment
-
Replace the image placeholder in the
breeze-agent-aks.yamlmanifest with your image value -
Apply the manifest:
kubectl create -f breeze-agent-aks.yaml
GKE
Requirements
Ensure the cluster has permission to pull images from your container registry. You may use one of the following:
-
Workload Identity
-
Image pull secrets
Deployment
-
Replace the image placeholder in the
breeze-agent-gke.yamlmanifest with the actual image value. -
Apply the manifest:
kubectl create -f breeze-agent-gke.yaml