| Info |
|---|
This article instructs on explains how to install a 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. |
...
. As a result, Breeze will be installed on all hosts within the cluster. NOTE: Linux only, except for AL2023, which is not currently supported. |
| Table of Contents |
|---|
Introduction
Deployment of the Breeze agent on a Kubernetes cluster serves two purposes:
To discover Kubernetes assets (nodes, pods, etc.) within a private Kubernetes cluster by establishing a TunHub connection.
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. Log in to Cloudaware account . Select Admin under your username in the upper right corner→ Admin.
...
2. Locate Find Breeze in the list of DevOps Integrations → . Click 1 Configured.
...
3. Select the file for Linux* Agent version to download the Breeze agent.
...
:
...
*This integration is for Linux only.
...
| Code Block |
|---|
# 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:
| Code Block |
|---|
# 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 stepIMAGE_PULL_SECRET_NAME - name of the Kubernetes secret containing auth data of the private registry
...
| Code Block |
|---|
# 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 : ensure that Cloudaware has required permissions using this guide.
Azure AKS: ensure that Cloudaware has required permissions for Amazon EKS using this guide.
| Note |
|---|
Please allow 1 hour for the data to load into Cloudaware. |
...