How GitOps controllers detect drift and sync
WHAT IT TESTS: reconciliation mechanics. OUTLINE: the controller renders desired manifests from Git, diffs them against live cluster objects, marks OutOfSync, then a sync applies the diff to converge. RED FLAG: thinking it only acts on Git commits.
WHAT IT TESTS: whether you understand continuous diffing and reconciliation. ANSWER OUTLINE: the controller periodically renders the desired manifests from Git, fetches live objects from the API server, and compares them field by field; any difference marks the app OutOfSync, whether caused by a new commit or a manual cluster edit. A sync applies the rendered manifests so live state converges to desired, honoring sync waves, hooks, and prune. RED FLAG: claiming drift is only detected on Git changes, ignoring manual-edit drift.
Read the original → interview
- #gitops
- #argocd
- #flux
- #reconciliation
- #drift
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.