configuration drift

The slow, unrecorded way machines end up with different versions and settings from each other.

In more detail

Drift happens when people change machines by hand, updates land unevenly, or settings are copied imperfectly, so after a while no two machines match and nobody can say what one contains. Describing machines in version-controlled files and reapplying that description regularly both prevents drift and reveals it.

Examples

Running the same playbook hourly finds drift: a task that suddenly reports changed on one host marks a machine somebody edited by hand.
Repeated manual repair of the same drift is toil. A GitOps controller reports drift between desired and observed state, separately from application health.
A console hotfix changes a security group; the next terraform plan shows the difference
Drift makes baselines stale, so validators start failing healthy hosts or passing changed ones.
In Terraform, drift means real infrastructure has been changed outside Terraform, so it no longer matches state and configuration. The refresh at the start of each plan detects it; you then either change the configuration to accept it or apply to put things back. Copying a directory per environment is another source of drift, which is why variables exist.

Related terms

Related guides

Taught in

References

Certification courses