Don't Panic: Getting Your Infrastructure Drift Under Control
summary
Claims that 90% of large IaC deployments show drift and that 50% of those drifts go unnoticed, with concrete fixes: run terraform plan with detailed-exitcode on a schedule to detect changes, emit the plan file and alert (demo shows a nodePort changed to LoadBalancer detected within ~20s), or use Argo or Flux reconcilers for Kubernetes to auto-override manual edits. Also mentions driftctl, CloudFormation’s built-in detection, and routing alerts to the right team for safe resolution.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:42Infrastructure as Code
- 2:27Infrastructure Drift
- 6:08Manual Change during an Emergency Fix
- 7:36Automated Application
- 8:34Partial Adoption
- 10:21Misalignment between the Infrastructure Score Tool and the Cloud Api
- 14:12Aligning the Cloud with the Infrastructure as Code
- 18:52Terraform Workspace
- 19:12Kubernetes Deployment
related talks
31mWhy You Should Take Care of Infrastructure Drift
24mWhy you should take care of infrastructure drift
30mWhy you should take care of infrastructure drift
27mThe State of Infrastructure Drift: What We Learned From 100+ DevOps Teams
21mFrom Ghost Assets to Infrastructure Drift - Don't Get Spooked
32mManaging Terraform resource drift using the GitOps method
29mManaging infrastructure with Git: First principles of GitOps
26mTerraform Config Drift How to Handle Out of Band Infrastructure Changes