Comparison
GitOps driftvsInfrastructure drift
GitOps drift
someone scaled the deployment by hand during a spike and the agent scaled it straight back down, twice.
Divergence between the repository's declared state and the cluster's actual state, which a reconciling agent will correct without being asked. It makes emergency manual intervention a fight with automation, and the resolution is either to commit the change or to pause reconciliation deliberately for the duration. Teams that do neither spend an incident wondering why their fix keeps disappearing.
Full entry →Infrastructure drift
somebody fixed it in the console during an incident, and the next apply politely undid the fix.
Divergence between what the code declares and what actually exists, caused by manual changes, other automation or the provider itself. It is inevitable in any estate humans can still reach, and its danger is not the change itself but the next apply, which will reconcile it away without anyone connecting the two events. The incident-time console fix is the classic instance and the reason a follow-up code change belongs in the incident's action list.
Full entry →