This article instructs on how to install Cloudaware Breeze agent on a Kubernetes cluster running in a private network. One sample of Breeze agent will be installed on a cluster automatically enabling TunHub Gateway on it. Linux only.

Breeze Agent Setup

1. Log in to Cloudaware account. Select Admin under your username in the upper right corner.

2. Locate Breeze in the list of DevOps Integrations → 1 Configured.

3. Select Linux* Agent version to download the Breeze agent.

*This integration is for Linux only.

4. Clone or download the breeze-tools repository from Cloudaware GitHub repo:

# git clone https://github.com/cloudaware/breeze-tools.git
CODE

5. Change the working directory to kubernetes, put the archive with Breeze agent installer and then extract it:

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

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 .
CODE


In order to check if images have been generated, the following command can be used:

# docker images "breeze*"
CODE

7. Create two repositories named 'breeze-agent' and 'breeze-agent-init' in your private Docker registry.

8. Push the created images to the PRIVATE Docker container registry:

# docker tag breeze-agent-init:latest CONTAINER_REGISTRY_URI/breeze-agent-init:latest
# docker push breeze-agent-init:latest CONTAINER_REGISTRY_URI/breeze-agent-init:latest
# docker tag breeze-agent:latest CONTAINER_REGISTRY_URI/breeze-agent:latest
# docker push breeze-agent:latest CONTAINER_REGISTRY_URI/breeze-agent:latest
CODE

WHERE

CONTAINER_REGISTRY_URI 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 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

10. Apply the configuration:

# kubectl create -f breeze-agent-deployment-eks.yaml
CODE

Integration Status Check

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 EKS/AKS

Amazon EKS: ensure that Cloudaware has required permissions using this guide

Azure AKS: ensure that Cloudaware has required permissions using this guide.

Please allow 1 hour for the data to load into Cloudaware.