Kubernetes DaemonSet

Use this playbook to deploy Breeze as a DaemonSet so every Kubernetes node runs the agent.

Prerequisites

• A Kubernetes cluster (EKS, AKS, GKE, or self-hosted) with:
  • Linux worker nodes supported by Breeze.
  • Outbound access from nodes to Breeze endpoints.
• Access to a container registry for Breeze images.

Build and Push Images

1. In Cloudaware, go to Admin.
2. Find Breeze in DevOps Integrations. Click CONFIGURED.
3. Download the installer.
4. Clone the Breeze tools repo (or obtain your organization’s equivalent Kubernetes helper files).
5. In the Kubernetes/DaemonSet folder:
   • Copy the Breeze archive into the folder and extract it so the breeze-agent directory is present.
   • Build Breeze images (for example, init + agent, or a single DaemonSet image) and tag them for your registry.
6. Push the images to your container registry.

Apply DaemonSet + RBAC

1. Update the DaemonSet manifest to reference:
   • Your registry image URLs.
   • Image pull secrets (if required).
   • Target namespace and labels.
2. Apply the manifest:
   • kubectl apply -f ds-breeze-agent.yaml (or equivalent).
3. Ensure RBAC is scoped so Breeze pods can access node‑level resources they need, but not cluster‑wide admin privileges.

Validate Health

• Check DaemonSet status:
  • kubectl get ds -n <namespace> and confirm DESIRED = CURRENT = READY.
• Inspect pod logs:
  • kubectl logs -n <namespace> <breeze-pod> to confirm successful runs and no recurring errors.
• In Cloudaware:
  • Verify that Kubernetes nodes report Breeze facts and that any TunHub‑backed integrations see the cluster if applicable.

Roll Updates

• Build and tag new Breeze images when upgrading the agent or configuration.
• Update the DaemonSet manifest (or image tag) and apply the change.
• Use a rolling update strategy (default for DaemonSets) to replace pods while maintaining coverage.