Rolling Back Failed Deployments
Understand the reasons for rolling back Kubernetes deployments, including critical bugs and failed Pod creations. Learn how to verify deployment status with kubectl rollout commands and use automated checks to decide when to undo failed updates.
We'll cover the following...
Why should we roll back?
Discovering a critical bug is probably the most common reason for a rollback. Still, there are others. For example, we might be in a situation where Pods cannot be created. An easy to reproduce case would be an attempt to deploy an image with a tag that does not exist. Let’s update the definition of our image and deploy it again:
Let's update the definition of our Image and deploy it again.
The output is as follows:
After seeing such a message, you might be under the impression that everything is working properly. However, that output only indicates that the definition of the image used in the Deployment was successfully updated. That does not mean that the Pods behind the ...