A Deployment rollout appears stuck: new Pods remain Pending while old Pods still serve traffic. Image name and tags look correct. What should the candidate investigate first for this failure mode?
Select an answer to reveal the explanation.
Short Explanation
Sometimes the movers can’t even get into the building—no parking, no elevator—not because the furniture is wrong. Pending usually means scheduling/resources; check events before blaming the image tag again.
Full Explanation
Rollouts stall when new Pods never become Ready, and Pending commonly indicates the scheduler cannot place them (resource pressure, affinity, taints, PVCs). Inspecting kubectl describe/events for Insufficient cpu/memory or similar is the right next step when the image reference already looks valid. revisionHistoryLimit, deleting CoreDNS, or making a Service headless do not fix scheduling pressure.