Desired state vs actual state reconciliation in Kubernetes - Quick Revision & Key Differences

Recall & Review

beginner

What is the 'desired state' in Kubernetes?

The desired state is the configuration you declare for your cluster, like how many pods should run or which images to use. Kubernetes tries to make the actual state match this desired state.

beginner

What does 'actual state' mean in Kubernetes?

The actual state is what is really happening in the cluster right now, such as how many pods are running and their current status.

intermediate

How does Kubernetes use reconciliation to manage the cluster?

Kubernetes constantly compares the actual state to the desired state. If they differ, it takes actions to fix the actual state to match the desired state. This process is called reconciliation.

beginner

Why is reconciliation important in Kubernetes?

Reconciliation ensures the cluster stays healthy and works as expected, even if something breaks or changes unexpectedly. It’s like a thermostat keeping room temperature steady.

beginner

Give an example of reconciliation in Kubernetes.

If you want 3 pods running but one crashes, Kubernetes notices only 2 are running (actual state). It then starts a new pod to reach 3 pods (desired state).

What does Kubernetes do when the actual state differs from the desired state?

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

B It ignores the difference.

C It changes the desired state to match the actual state.

D It shuts down the cluster.

Kubernetes acts to fix the actual state so it matches the desired state, ensuring the cluster behaves as expected.

Which of these best describes the 'desired state'?

A The configuration you want for your cluster.

B The logs of the cluster.

C The current number of running pods.

D The hardware specs of the nodes.

The desired state is the configuration you declare, like how many pods should run.

What is reconciliation in Kubernetes?

A A method to scale nodes manually.

B A process to backup data.

C A way to update Kubernetes software.

D A process to compare and fix states.

Reconciliation means Kubernetes compares actual and desired states and fixes differences.

If a pod crashes, what will Kubernetes do during reconciliation?

A Delete all pods.

B Start a new pod to replace the crashed one.

C Do nothing and wait for manual restart.

D Change the desired state to fewer pods.

Kubernetes will start a new pod to maintain the desired number of pods.

Why is the reconciliation loop important for cluster health?

A It prevents any changes in the cluster.

B It slows down the cluster.

C It ensures the cluster matches the desired configuration.

D It deletes unused resources automatically.

The reconciliation loop keeps the cluster running as intended by fixing differences between actual and desired states.

Explain in your own words how Kubernetes uses reconciliation to keep the cluster running smoothly.

Think about how a thermostat keeps room temperature steady.

Describe a real-life example that helps you understand the difference between desired state and actual state in Kubernetes.

Imagine setting a goal and checking if reality matches it.

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