A parks department Deployment hangs after a bad container image was rolled out. Which action restores traffic using the previous ReplicaSet revision?
Select an answer to reveal the explanation.
Short Explanation
Bad paint job on the new storefront? Roll the shutter back to yesterday’s look. kubectl rollout undo puts the Deployment back on the previous ReplicaSet so users see the last known-good revision instead of waiting on a broken image.
Full Explanation
kubectl rollout undo Deployment/<name> rolls the Deployment back to the previous revision by reactivating the prior ReplicaSet and scaling down the failed one. That is the intended recovery path when a new image or template change leaves the rollout stuck. Lengthening progressDeadlineSeconds does not fix a bad image, emptying Service selectors drops traffic without restoring a good revision, and recreating from memory skips the tracked revision history.