In kubernetes, if you do a rolling update to upgrade container images of your pods via following command (note deployment is called "kubernetes-bootcamp"):
kubectl set image deployment.v1.apps/kubernetes-bootcamp kubernetes-bootcamp=gcr.io/google-sample/kubernetes-bootcamp:v2
Assume update went bad (i.e. one or more pods are down post-update), issue command to roll back to imediate previous version
kubectl rollout undo deployment kubernetes-bootcamp
In kubernetes, if you do a rolling update to upgrade container images of your pods via following command (note deployment is called "kubernetes-bootcamp"):
kubectl set image deployment.v1.apps/kubernetes-bootcamp kubernetes-bootcamp=gcr.io/google-sample/kubernetes-bootcamp:v2
Assume update went bad (i.e. one or more pods are down post-update), issue command to roll back to imediate previous version
In kubernetes, if you do a rolling update to upgrade container images of your pods via following command (note deployment is called "kubernetes-bootcamp"):
kubectl set image deployment.v1.apps/kubernetes-bootcamp kubernetes-bootcamp=gcr.io/google-sample/kubernetes-bootcamp:v2
Assume update went bad (i.e. one or more pods are down post-update), issue command to roll back to imediate previous version
kubectl rollout undo deployment kubernetes-bootcamp
| status | not learned | measured difficulty | 37% [default] | last interval [days] | |||
|---|---|---|---|---|---|---|---|
| repetition number in this series | 0 | memorised on | scheduled repetition | ||||
| scheduled repetition interval | last repetition or drill |