[Solved] You want to update a Deployment's container image from nginx:1.19 to nginx:1.21.... What explains this behavior in terms of desired vs actual state reconciliation? | Kubernetes

Kubernetes - Fundamentals

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?

AKubernetes ignores image changes unless manually restarted.

BKubernetes gradually updates pods to match desired state using rolling updates.

CKubernetes cannot update pods without deleting the Deployment.

DKubernetes immediately deletes all old pods and creates new ones.

Step-by-Step Solution

Solution:

Step 1: Understand rolling update strategy
Kubernetes uses rolling updates to gradually replace old pods with new ones to avoid downtime.
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.
Final Answer:
Kubernetes gradually updates pods to match desired state using rolling updates. -> Option B
Quick Check:
Rolling update means gradual pod replacement [OK]

Quick Trick: Rolling updates replace pods gradually [OK]

Common Mistakes:

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

Master "Fundamentals" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

More Kubernetes Quizzes

What explains this behavior in terms of desired vs actual state reconciliation?

Step 1: Understand rolling update strategy

Step 2: Explain why old pods remain temporarily

Final Answer:

Quick Check:

Want More Practice?