reconciliation
The repeated check-and-fix loop in which a program compares desired state with observed state and changes the world to match.
In more detail
Every Kubernetes controller runs this loop: watch the objects it owns, notice a difference, take one step to reduce it, and check again. Because the loop keeps running, a deleted pod or a lost node is repaired without anyone typing a command. GitOps tools and operators use the same idea with a Git repository or a custom resource as the source of desired state.
Examples
A Kubernetes ReplicaSet controller sees two pods where three are wanted and creates one.In Terraform: Each Terraform plan proposes a reconciliation between configuration and reality, and apply carries it out. The same idea drives Kubernetes controllers, which reconcile continuously instead of when someone runs a command.Related terms
- desired state — A description of how a machine should look when the work is finished, rather than a list of steps to get there.
- Kubernetes controller — A program inside or alongside the cluster that watches one kind of object and keeps acting until reality matches what that object asks for.
- self heal — An Argo CD option that re-applies the desired state when someone changes a live resource by hand.
- operator pattern — Packaging operational knowledge as a custom resource plus a controller that reconciles it, so software manages itself on Kubernetes.
- GitOps — Operating a system by keeping its desired state in Git and letting a controller continuously make the live system match it.
- state drift — When a system's actual state has moved, or is moving, away from its desired state.
- feedback loop — How previous attempts to apply the desired state have affected the actual state, read back to decide the next action.
- Continuously Reconciled — The fourth GitOps principle: software agents continuously observe actual system state and attempt to apply the desired state.
- terraform plan — The command that compares configuration, state and reality and prints the actions needed to make them match, without changing anything.
- configuration drift — The slow, unrecorded way machines end up with different versions and settings from each other.
Taught in
- How The Exam Works: Weights, Pacing And A Plan — Certified Argo Project Associate (CAPA) Exam Prep
- What Argo Workflows Runs: Controller, Server And One Pod A Step — Certified Argo Project Associate (CAPA) Exam Prep
- Argo CD: Components, Applications And Projects — Certified Argo Project Associate (CAPA) Exam Prep
- Sync: Manual Or Automated, Prune And Self-Heal — Certified Argo Project Associate (CAPA) Exam Prep
- ApplicationSets And The App Of Apps — Certified Argo Project Associate (CAPA) Exam Prep
- Health, Reconciliation And Fields Argo CD Should Ignore — Certified Argo Project Associate (CAPA) Exam Prep
- A Hotfix At 3 A.M.: Who Wins At 3:05? — Certified GitOps Associate (CGOA) Exam Prep
- Staging Is Gone: Desired State, Declarations And The State Store — Certified GitOps Associate (CGOA) Exam Prep
- Three Edits At 2 A.M.: Drift And Reconciliation — Certified GitOps Associate (CGOA) Exam Prep
- Sixteen Pods, Room For Twelve: The System, Feedback And Continuous — Certified GitOps Associate (CGOA) Exam Prep
- Two Ways Back From 2.5: Rollback The GitOps Way — Certified GitOps Associate (CGOA) Exam Prep
- Terminology Sprint: One Incident, Nine Terms — Certified GitOps Associate (CGOA) Exam Prep
- Seven Steps Called GitOps: The Declarative Principle — Certified GitOps Associate (CGOA) Exam Prep
- Someone Cleaned Up The History: Versioned And Immutable — Certified GitOps Associate (CGOA) Exam Prep
- Twelve Keys To Production: Pulled Automatically — Certified GitOps Associate (CGOA) Exam Prep
- An Hour Without Payments: Continuously Reconciled — Certified GitOps Associate (CGOA) Exam Prep
- Principles Sprint: Six Setups, One Question — Certified GitOps Associate (CGOA) Exam Prep
- Two Clicks Nobody Wrote Down: Configuration And Infrastructure As Code — Certified GitOps Associate (CGOA) Exam Prep
- What Does CI Still Do? CI, CD And Where GitOps Starts — Certified GitOps Associate (CGOA) Exam Prep
- Related Practices Sprint: One Change, Five Practices — Certified GitOps Associate (CGOA) Exam Prep
- Thursday, With A Way Back: Promotion, Deploy And Release — Certified GitOps Associate (CGOA) Exam Prep
- Three Minutes Of Waiting: Pull Versus Event-Driven — Certified GitOps Associate (CGOA) Exam Prep
- Three Regions By Spring: GitOps Architecture — Certified GitOps Associate (CGOA) Exam Prep
- Patterns Sprint: Eight Needs, One Pattern Each — Certified GitOps Associate (CGOA) Exam Prep
- Three Teams, Three Formats: Manifests And Packaging — Certified GitOps Associate (CGOA) Exam Prep
- A Bucket Nobody Wrote Down: State Stores Beyond Git — Certified GitOps Associate (CGOA) Exam Prep
- A Bake-Off With One Rule: Argo CD And Flux — Certified GitOps Associate (CGOA) Exam Prep
- A Rollback Nobody Heard: Notifications, Observability And CI — Certified GitOps Associate (CGOA) Exam Prep
- Tooling Sprint: The CTO's Shopping List — Certified GitOps Associate (CGOA) Exam Prep
- Forty-Six Of Sixty: The Mock And What It Tells You — Certified GitOps Associate (CGOA) Exam Prep
- The Evening Before: Final Review — Certified GitOps Associate (CGOA) Exam Prep
- The Push Model vs. The Pull Model — Continuous Integration & Continuous Delivery Pipelines
- What is GitOps? — Continuous Integration & Continuous Delivery Pipelines
- Argo CD Architecture and Applications — Continuous Integration & Continuous Delivery Pipelines
- Flux as the Alternative — Continuous Integration & Continuous Delivery Pipelines
- Containers And Orchestration Context — DevOps & Site Reliability Engineering
- Pipelines And GitOps Context — DevOps & Site Reliability Engineering
- From Docker To Desired State — Kubernetes: Production-Grade Container Orchestration
- Control Plane: etcd, API Server, Scheduler, Controllers — Kubernetes: Production-Grade Container Orchestration
- Worker Nodes: kubelet, Runtime, CNI And kube-proxy — Kubernetes: Production-Grade Container Orchestration
- Namespaces, Labels And Declarative Manifests — Kubernetes: Production-Grade Container Orchestration
- Troubleshooting: API Server And Control Plane Failures — Kubernetes: Production-Grade Container Orchestration
- Argo CD Applications And Flux Reconciliation — Kubernetes: Production-Grade Container Orchestration
- A Tiny CRD, Controller And The Operator Pattern — Kubernetes: Production-Grade Container Orchestration
- Troubleshooting: GitOps Drift And Controller Failures — Kubernetes: Production-Grade Container Orchestration
- What State Really Is And Why It Is Needed — Infrastructure as Code with Terraform
- Simulating A Managed Database — Infrastructure as Code with Terraform
- Detecting And Fixing Configuration Drift — Infrastructure as Code with Terraform
- Importing Existing Resources — Infrastructure as Code with Terraform
- Forcing Replacement — Infrastructure as Code with Terraform