[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"glossary-infrastructure-drift::en":3,"gloss-cluster-infrastructure-drift::en":26,"gloss-next-infrastructure-drift::en":9},{"slug":4,"category":5,"name":6,"definition":7,"meta_desc":8,"faq":9,"schema_markup":9,"related":10},"infrastructure-drift","cloud","Infrastructure Drift","Infrastructure drift is the gap between the infrastructure your code declares and the infrastructure that actually exists. Declarative tooling promises that the files are the truth, and that promise holds only while every change goes through the files. It stops holding the first time somebody widens a security group by hand during an incident, a managed service updates a default on your behalf, or a resource is created through a console because the pipeline was slow that afternoon. Drift is dangerous less because the environment is wrong and more because the record is. A rebuild from the declared state silently removes the manual fix nobody wrote down, so an incident is resolved on Tuesday and reintroduced on Friday by a routine apply. Disaster recovery inherits the same problem in a worse form: the environment you can rebuild is the declared one, and if production has drifted, the rebuilt environment is not production. Reviews also degrade, because reviewing a change to a file that no longer describes reality is theater. Detection is a scheduled comparison rather than a one-time cleanup. Most tools can produce a plan or diff against live state, and running it on a schedule and alerting on any non-empty result is what converts drift from an archaeology project into a small daily correction. Reconciliation goes in one of two directions and the choice should be deliberate: adopt the manual change by writing it into code, or revert it, and record which was chosen and why. Prevention is mostly access. Read-only console access for humans in production, changes through the pipeline, and a documented break-glass path for emergencies that requires the change to be codified afterward, closes the loop that produced the drift in the first place.","Infrastructure drift is the gap between declared and actual infrastructure: why a rebuild silently deletes the manual fix, and how scheduled diffs catch it.",null,[11,14,17,20,23],{"slug":12,"name":13},"environment-variable","Environment Variable",{"slug":15,"name":16},"gitops","GitOps",{"slug":18,"name":19},"infrastructure-as-code","Infrastructure as Code (IaC)",{"slug":21,"name":22},"rollback","Rollback",{"slug":24,"name":25},"runbook","Runbook",[27,31,34,37,41,44,47,50,53,56,59,62],{"slug":28,"category":5,"name":29,"updated_at":30},"autoscaling","Autoscaling","2026-08-24T02:46:37+00:00",{"slug":32,"category":5,"name":33,"updated_at":30},"availability-zone","Availability Zone (AZ)",{"slug":35,"category":5,"name":36,"updated_at":30},"block-storage","Block Storage",{"slug":38,"category":5,"name":39,"updated_at":40},"disaster-recovery","Disaster Recovery","2026-08-24T02:46:38+00:00",{"slug":42,"category":5,"name":43,"updated_at":40},"edge-ai","Edge AI",{"slug":45,"category":5,"name":46,"updated_at":30},"egress-fees","Egress Fees (Data Transfer Out)",{"slug":48,"category":5,"name":49,"updated_at":30},"finops","FinOps (Cloud Financial Operations)",{"slug":51,"category":5,"name":52,"updated_at":40},"immutable-infrastructure","Immutable Infrastructure",{"slug":54,"category":5,"name":55,"updated_at":30},"managed-kubernetes","Managed Kubernetes",{"slug":57,"category":5,"name":58,"updated_at":30},"multi-region","Multi-Region",{"slug":60,"category":5,"name":61,"updated_at":40},"noisy-neighbor","Noisy Neighbor",{"slug":63,"category":5,"name":64,"updated_at":30},"platform-as-a-service","Platform as a Service (PaaS)"]