Question

A platform engineer manages a Deployment named 'payments-api'. After several rolling updates, they attempt to roll back two revisions using 'kubectl rollout undo deployment/payments-api --to-revision=3', but the command fails with an error stating that the revision was not found. Running 'kubectl rollout history deployment/payments-api' shows only the two most recent revisions. What is the most likely cause?

Accepted Answer

The Deployment's spec.revisionHistoryLimit is set to a low value, so older ReplicaSets (and their revisions) were garbage-collected.

Answer

Rollbacks to a specific revision are only supported for StatefulSets, not Deployments.

Answer

The Deployment uses the Recreate strategy, which does not retain any revision history.

Answer

The --to-revision flag must be set to 0 to roll back to any previous revision.