The dashboard was green yesterday. Today it’s red. Nothing in the Git repo changed.
That’s drift. And if you’re running infrastructure as code (IaC), it’s the silent threat waiting to consume your confidence in every deployment. Terraform, CloudFormation, Pulumi—none of them save you from drift. They just make it easier to deploy the version you think you have, not the one actually running.
Drift detection is the anchor in this storm. Without it, configs decay under the weight of hotfixes, out-of-band changes, and human shortcuts. You lose auditability. You lose reproducibility. In Kubernetes, even more so—because clusters are living systems. Manual changes sneak in through kubectl, CI jobs push patches, and controllers mutate objects without touching Git.
That’s where K9S and drift detection make a lethal combination. K9S gives you an interactive lens on your live cluster state, resource by resource. IaC drift detection compares that state against what’s declared in source control. The moment a delta appears—maybe a ConfigMap updated outside the pipeline—it’s visible and actionable. You’re no longer discovering brokenness at 2 a.m. after an outage; you see it in real time.