An administrator observes that a recent container image update to a Google Kubernetes Engine (GKE) deployment named `web-app` introduced application errors. The administrator needs to inspect the revision history, roll back the deployment to the previous working revision, and confirm that the rollback completes successfully. What is the correct chronological sequence of `kubectl` commands to perform this operation?
- 1Inspect the revision history of the deployment using `kubectl rollout history deployment/web-app`.
- 2Revert the deployment to its previous stable revision using `kubectl rollout undo deployment/web-app`.
- 3Verify that the rollback operation has finished successfully using `kubectl rollout status deployment/web-app`.
Answer
The correct sequence of operations is: First, inspect the revision history (`kubectl rollout history deployment/web-app`). Second, execute the rollback to the previous revision (`kubectl rollout undo deployment/web-app`). Third, monitor and verify the rollout status (`kubectl rollout status deployment/web-app`).
When managing GKE workloads, the proper sequence for restoring a failed deployment rollout is: 1) inspect the revision history to identify previous versions (`kubectl rollout history`), 2) revert the deployment to the previous revision (`kubectl rollout undo`), and 3) monitor the progress until completion (`kubectl rollout status`).
Step-by-Step Solution
Key Concept
GKE Deployment Rollback Operations