Page Comparison

...

# cd breeze-tools/kubernetes/
# cp /path/to/agent/distro/breeze-agent.x86_64.linux.tgz .
# tar xf breeze-agent.x86_64.linux.tgz

WHERE

breeze-agent.x86_64.linux.tgz should be replaced by the name of the dowloaded installer file (e.g. breeze-agent.1x11xx1xxxx11x11111x1x1x.11111111.0.x86_64.linux.tgz).

6. Build docker images:

# docker build -t breeze-agent-init -f Dockerfile.breeze-agent-init .
# docker build -t breeze-agent -f Dockerfile.breeze-agent .

...

WHERE

CONTAINER_REGISTRY_URI - the fully qualified path to the private registry with the repositories should be replaced by your private container registry URI (e.g. 111111111111.dkr.ecr.us-east-1.amazonaws.com/breeze-agent).

9. Open file breeze-agent-deployment-eks.yaml (for Amazon EKS) or breeze-agent-deployment-aks.yaml (for Azure AKS) in the text editor and replace the following placeholders with proper valid values:

CONTAINER_REGISTRY_URI - same as in the previous step
IMAGE_PULL_SECRET_NAME - name of the Kubernetes secret containing auth data of the private registry

...

Once Breeze is installed, Cloudaware automatically enables TunHub Gateway for a secure connection with Kubernetes which may be running in a private network.

Go back to Cloudaware Admin → Clouds & Integrations → TunHub. Ensure that the TunHub connection has been created and has a green status. 

...

Checking Cloudaware Access To Cluster

Amazon EKS: Ensure that Cloudaware has required permissions this guide.

Azure AKS: Ensure that Cloudaware has required permissions for Amazon EKS using this guide.

...