A permitting UI team needs to inspect past Deployment revisions and then undo to a specific older revision—not only the immediate previous one. Which approach matches that goal?
Select an answer to reveal the explanation.
Short Explanation
Revisions are like numbered blueprints in a drawer—look at the list, then pull the blueprint you want. rollout history shows the revisions; undo --to-revision puts that specific one back in play.
Full Explanation
kubectl rollout history deployment/<name> lists retained revisions (bounded by revisionHistoryLimit). kubectl rollout undo deployment/<name> --to-revision=<n> restores a chosen revision rather than only stepping back one. Pod logs and metrics do not store Deployment revision history, and deleting old ReplicaSets removes the undo targets you need.