CDEvents in Action #5: The Kubernetes Deployment Blind Spot

ArgoCD gives you GitOps visibility. But what about the operator who ran kubectl apply during an incident? Or the platform team's helm upgrade ? Those are invisible — and they're the ones that tend to cause problems. The Gap ArgoCD Leaves In Episode #4 , you learned to capture CDEvents passively from ArgoCD webhooks — no pipeline changes, instant visibility into GitOps deployments. But ArgoCD only sees what ArgoCD manages. In a real cluster, deployments happen in multiple ways: kubectl apply -f deployment.yaml — ops team responding to an incident helm upgrade payment-api ./chart — platform team releasing a patch kubectl set image deployment/api api=v2.1.0 — someone testing a hotfix ArgoCD sync — your GitOps flow Only the last one shows up in ArgoCD. The first three are invisible. This isn't a criticism of ArgoCD. It's the right tool for what it does. The gap is that your cluster has more activity than your GitOps tool manages . What Native Kubernetes Monitoring Adds Instead of watching