liveBook · Manning

Reconciliation

As explained in Learn Docker in a Month of Lunches, Second Edition

A reconciliation loop is a control loop that repeatedly compares current system state with desired state and takes corrective action.

A reconciliation loop repeatedly compares a system’s current state with its desired state and takes corrective action. In Kubernetes, a Deployment notices when its Pods do not match the declared model and creates replacements. Services also update their endpoints when matching Pods change. section 15.3

Delete a Pod and watch Kubernetes recover

Apply a Deployment, then run `kubectl delete pod -l app=numbers`. Listing the Pods again shows a replacement with a different name. The Service redirects traffic to the new Pod, demonstrating resilience through reconciliation. section 15.3

How Learn Docker in a Month of Lunches, Second Edition covers it

How deep it goes
Explains the control-loop behavior through Pod replacement and endpoint updates, without descending into controller internals.
Examples
Demonstrates Pod deletion, automatic replacement, scaling to three replicas, endpoint updates, and traffic distribution.
What it assumes
Assumes familiarity with Kubernetes Pods and Services while introducing Deployments through their desired-state model.
What you can do after
Operate/configure Deployments and verify reconciliation by deleting Pods, scaling replicas, and inspecting replacement endpoints.
How it connects
Connects desired state with Kubernetes Deployments, Pods, Services, selectors, replicas, and health checks.

Also explained in

Compare how 7 books explain reconciliation →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Learn Docker in a Month of Lunches, Second Edition. The section links point to the parts of the book it draws on.