Desired state vs actual state reconciliation in Kubernetes - When to Use Which

The Big Idea

What if your system could fix itself whenever things go wrong, without you doing a thing?

The Scenario

Imagine you have a garden where you want exactly 10 rose bushes, 5 tulips, and 3 sunflowers. Every day, you check the garden and manually plant or remove flowers to keep it perfect.

The Problem

This manual checking is tiring and easy to mess up. You might forget to remove a weed or plant a missing flower. It takes a lot of time and you can never be sure the garden matches your plan exactly.

The Solution

With desired state vs actual state reconciliation, you simply tell the system your perfect garden plan once. The system then watches the garden and automatically fixes any differences, planting or removing flowers as needed without you lifting a finger.

Before vs After

✗ Before

Check garden daily; if flowers missing, plant; if extra, remove

✓ After

Declare desired garden state; system auto-corrects actual garden

What It Enables

This approach lets you trust the system to keep things exactly how you want, freeing you to focus on other tasks.

Real Life Example

In Kubernetes, you declare how many copies of an app you want running. The system constantly checks and starts or stops copies to match your desired number automatically.

Key Takeaways

Manual fixes are slow and error-prone.

Reconciliation automates matching actual state to desired state.

This ensures systems stay correct and reliable without constant manual work.

Practice

1. What does Kubernetes do when the actual state of a pod differs from the desired state?

easy

A. It changes the actual state to match the desired state automatically.

B. It deletes the pod without recreating it.

C. It ignores the difference and does nothing.

D. It sends an alert but does not change anything.

Solution

1. Step 1: Understand desired vs actual state

   The desired state is what you want Kubernetes to have running, and the actual state is what is currently running.

2. Step 2: Kubernetes reconciliation process

   Kubernetes continuously compares actual state to desired state and makes changes to fix any differences automatically.

3. Final Answer:

   It changes the actual state to match the desired state automatically. -> Option A

4. Quick Check:

   Reconciliation means fixing actual state to desired state [OK]

Hint: Kubernetes fixes differences automatically [OK]

Common Mistakes:

• Thinking Kubernetes ignores differences
• Believing Kubernetes only alerts without fixing
• Assuming Kubernetes deletes pods without recreating

2. Which Kubernetes component is responsible for ensuring the actual state matches the desired state?

easy

A. kube-apiserver

B. kube-scheduler

C. etcd

D. kube-controller-manager

Solution

1. Step 1: Identify the role of kube-controller-manager

   The kube-controller-manager runs controllers that watch the desired state and make changes to match the actual state.

2. Step 2: Differentiate other components

   kube-apiserver handles API requests, kube-scheduler assigns pods to nodes, and etcd stores cluster data but does not reconcile states.

3. Final Answer:

   kube-controller-manager -> Option D

4. Quick Check:

   Controllers fix state differences [OK]

Hint: Controllers fix state differences [OK]

Common Mistakes:

• Confusing scheduler with controller
• Thinking apiserver reconciles state
• Assuming etcd manages reconciliation

3. Given this YAML snippet for a Deployment:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: myapp
spec:
  replicas: 3
  selector:
    matchLabels:
      app: myapp
  template:
    metadata:
      labels:
        app: myapp
    spec:
      containers:
      - name: web
        image: nginx:1.19

If one pod crashes and stops running, what will Kubernetes do?

medium

A. Create a new pod to maintain 3 replicas.

B. Do nothing and keep 2 pods running.

C. Delete all pods and restart the deployment.

D. Scale down the deployment to 2 replicas.

Solution

1. Step 1: Understand the desired replicas

   The Deployment specifies 3 replicas, so Kubernetes wants 3 pods running.

2. Step 2: Reconciliation after pod crash

   If one pod crashes, Kubernetes detects the actual state has only 2 pods and creates a new pod to restore 3 replicas.

3. Final Answer:

   Create a new pod to maintain 3 replicas. -> Option A

4. Quick Check:

   Pods count fixed to desired replicas [OK]

Hint: Pods auto-recreated to match replicas [OK]

Common Mistakes:

• Thinking Kubernetes ignores crashed pods
• Assuming deployment restarts all pods
• Believing deployment scales down automatically

4. You notice a Deployment is stuck with fewer pods than desired. Which of these is a likely cause preventing reconciliation?

medium

A. The kube-apiserver is running normally.

B. The image name in the container spec is correct.

C. The Deployment's selector labels do not match pod labels.

D. The desired replicas count is set to 3.

Solution

1. Step 1: Check label selectors for matching pods

   If the Deployment's selector labels do not match pod labels, Kubernetes cannot track pods correctly, so reconciliation fails.

2. Step 2: Understand other options

   Correct image name, running apiserver, and desired replicas do not prevent reconciliation by themselves.

3. Final Answer:

   The Deployment's selector labels do not match pod labels. -> Option C

4. Quick Check:

   Label mismatch blocks reconciliation [OK]

Hint: Selector and pod labels must match [OK]

Common Mistakes:

• Ignoring label selector importance
• Blaming image name for pod count issues
• Assuming apiserver status causes pod count

5. You want to update a Deployment's container image from nginx:1.19 to nginx:1.21. After applying the change, you see some pods still run the old image. What explains this behavior in terms of desired vs actual state reconciliation?

hard

A. Kubernetes ignores image changes unless manually restarted.

B. Kubernetes gradually updates pods to match desired state using rolling updates.

C. Kubernetes cannot update pods without deleting the Deployment.

D. Kubernetes immediately deletes all old pods and creates new ones.

Solution

1. Step 1: Understand rolling update strategy

   Kubernetes uses rolling updates to gradually replace old pods with new ones to avoid downtime.

2. Step 2: Explain why old pods remain temporarily

   During rolling update, some pods run old image until replaced, so actual state temporarily differs from desired state.

3. Final Answer:

   Kubernetes gradually updates pods to match desired state using rolling updates. -> Option B

4. Quick Check:

   Rolling update means gradual pod replacement [OK]

Hint: Rolling updates replace pods gradually [OK]

Common Mistakes:

• Expecting instant pod replacement
• Thinking Deployment must be deleted to update
• Believing Kubernetes ignores image changes