Hands-On Microservices with Kubernetes

Rolling back standard Kubernetes deployments

Kubernetes deployments keep a history. For example, if we edit the user manager deployment and set the image version to 0.5, then we can see that there are two revisions now:

$ kubectl get po -l svc=user,app=manager -o jsonpath="{.items[0].spec.containers[0].image}" g1g1/delinkcious-user:0.5  $ kubectl rollout history deployment user-manager deployment.extensions/user-manager REVISION  CHANGE-CAUSE 1         <none> 2         <none>

The CHANGE-CAUSE column is not recorded by default. Let's make another change to version 0.4, but using the --record=true flag:

$ kubectl edit deployment user-manager --record=true deployment.extensions/user-manager edited  $ kubectl rollout history deployment user-manager deployment.extensions/user-manager ...