Page Comparison

Introduction

Deployment of the Breeze agent on a Kubernetes cluster serves two purposes:

1. To discover Kubernetes assets (nodes, pods, etc.) within a private Kubernetes cluster by establishing a TunHub connection. 

2. By deploying Breeze on a cluster through a daemon set, you install Breeze on all hosts within the cluster. Alternatively, you can achieve this by installing Breeze on individual EC2 instances.

Breeze Agent Setup

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

...

2. Find Breeze in the list of DevOps Integrations. Click 1 Configured.

...

2

...

3. Select the file for Linux*:

...

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

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

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

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

46. 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*"

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

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

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

WHERE where

CONTAINER_REGISTRY_HOSTNAME - the fully qualified path to the private registry with the repositories7. Open file 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 proper valid values:

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

810. Apply the configuration:

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

...

Check Status

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

...

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