After a bad OCIR tag hit the parks reservation Deployment, operators need the previous working Pods back quickly. Why does kubectl rollout undo succeed here?
Select an answer to reveal the explanation.
Short Explanation
A Deployment keeps yesterday's ReplicaSet in the wings like an understudy. kubectl rollout undo brings that cast back on stage. That is why you ship with a Deployment instead of hand-deleting Pods when a parks reservation image goes bad.
Full Explanation
Deployments keep prior ReplicaSets so a bad image or template change can be reversed with kubectl rollout undo or by reapplying the last good template. The retained ReplicaSet is the mechanism—not Terraform/Resource Manager state, not filesystem snapshots, and not manual Pod deletion (which would recreate from the current broken template). Rollback is a core reason to use a Deployment on OKE.