Rollback reverts a deployed workload to an earlier version or revision when an update fails. For a Deployment, kubectl rollout undo performs the reversal using the Deployment’s configured update strategy, so a RollingUpdate rollback replaces Pods gradually. section 15.2.6
Use rollback controls according to the workload and its update strategy:
- Undo the latest Deployment update with kubectl rollout undo deployment kiada; run it during an active rollout to cancel that rollout or afterward to revert it. section 15.2.6
- Inspect available revisions with kubectl rollout history deploy kiada, then examine a specific revision with --revision before selecting it. section 15.2.6
- Target an older revision explicitly with kubectl rollout undo deployment kiada --to-revision=1. section 15.2.6
- Treat OnDelete StatefulSet rollback as semi-automatic: delete each Pod yourself, allowing the controller to recreate it from the previous revision. section 16.3.3
Rolling back a Deployment
After a failed update, run kubectl rollout undo deployment kiada. Kubernetes restores the previous revision while respecting the Deployment strategy. To restore a particular earlier revision, inspect its Pod template and run kubectl rollout undo deployment kiada --to-revision=1. section 15.2.6
