Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This instruction is applicable to Kubernetes clusters running in EKS, other integrations are on the roadmap.

Breeze Agent Setup

1. Download the Breeze agent. Log in to Cloudaware account → Admin → Breeze → 1 Configured.

2. Clone or download the breeze-tools repository:

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

3. Change the working directory to kubernetes, put 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

4. Build docker images:

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


In order to check if images have been generated, the following command can be used: # docker images "breeze*"

5. Create two repositories named ‘breeze-agent’ and ‘breeze-agent-init’ in the private Docker registry.

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

# docker tag breeze-agent-init:latest CONTAINER_REGISTRY_HOSTNAME/breeze-agent-init:latest
# docker push breeze-agent-init:latest CONTAINER_REGISTRY_HOSTNAME/breeze-agent-init:latest
# docker tag breeze-agent:latest CONTAINER_REGISTRY_HOSTNAME/breeze-agent:latest
# docker push breeze-agent:latest CONTAINER_REGISTRY_HOSTNAME/breeze-agent:latest

where CONTAINER_REGISTRY_HOSTNAME - the fully qualified path to the private registry with the repositories

7. Open file breeze-agent-deployment.yaml in the text editor and replace the following placeholders with proper values:

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

8. Apply the configuration:

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

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

9. Check the status of your integration under Admin Console > TunHub > make sure the tunnel has been created and has a green status. 


  • No labels