CDEvents in Action #6: Monitor Every Kubernetes Deployment with One Helm Command

After this, every Deployment, StatefulSet, and DaemonSet change in your cluster generates a CDEvent automatically — no matter how it was deployed. Episode #5 explained the gap. This episode closes it. What You Need CDviz running with cdviz-collector reachable from inside the cluster Kubernetes v1.19+ with kubectl access Helm 3 The Command helm install cdviz-collector oci://ghcr.io/cdviz-dev/charts/cdviz-collector \ --set kubewatch.enabled = true \ --namespace cdviz \ --create-namespace That single flag ( kubewatch.enabled=true ) deploys kubewatch alongside cdviz-collector and wires them together: kubewatch watches Deployment/StatefulSet/DaemonSet changes cluster-wide (can be configured) cdviz-collector receives kubewatch CloudEvents and transforms them to CDEvents RBAC is configured automatically (read-only ClusterRole) See Kubernetes (via Kubewatch) Integration for details. Verify It Works 1. Check both pods are running: kubectl get pods -n cdviz # NAME READY STATUS # cdviz-collector-