Continuous Reconciliation
What you'll learn: How GitOps controllers automatically detect and fix differences between your desired infrastructure state (in Git) and the actual running state.
What Is Continuous Reconciliation?
In GitOps, continuous reconciliation is the automated process where a controller constantly compares what's running in your infrastructure against what's defined in your Git repository. When it detects a difference (called "drift"), it automatically corrects the running environment to match Git.
Think of it like a thermostat that continuously checks the room temperature against your desired setting and adjusts the heating or cooling to maintain that target—except instead of temperature, it's your entire infrastructure state.
How It Works
GitOps controllers run reconciliation loops on a schedule (often every few minutes or seconds):
- Fetch the desired state from Git (your declarative configuration)
- Observe the actual state in your cluster or cloud environment
- Compare the two states to detect drift
- Remediate by applying changes to bring actual state back to desired state
This happens continuously and automatically, without human intervention.
Why This Matters
Continuous reconciliation means your infrastructure is self-healing. If someone manually changes a configuration, the controller detects it and reverts it. If a pod crashes, the controller ensures replacements match your Git definition. This enforces Git as the single source of truth and prevents configuration drift.
Unlike traditional push-based deployments where you deploy once and hope nothing changes, continuous reconciliation actively maintains consistency over time.
Key Takeaway: Continuous reconciliation is the automated, ongoing process where GitOps controllers observe actual infrastructure state, compare it to Git's desired state, and automatically fix any drift—ensuring your environment always matches what's declared in version control.