In kubernetes, let's say you have 4 pods, in deployment "kubernetes-bootcamp", that are running container image "gcr.io/google-sample/kubernetes-bootcamp:v1", issue command to do rolling upgrade to image "gcr.io/google-sample/kubernetes-bootcamp:v2", fillout below occultions:
kubectl [...] [...] deployment.v1.apps/kubernetes-bootcamp kubernetes-bootcamp= [...]
NOTE: the kubernetes-bootcamp= part is referring to the conatiner name (which you can get from "kubectl describe deployment kubernetes-bootcamp"
kubectl set image deployment.v1.apps/kubernetes-bootcamp kubernetes-bootcamp=gcr.io/google-sample/kubernetes-bootcamp:v2
In kubernetes, let's say you have 4 pods, in deployment "kubernetes-bootcamp", that are running container image "gcr.io/google-sample/kubernetes-bootcamp:v1", issue command to do rolling upgrade to image "gcr.io/google-sample/kubernetes-bootcamp:v2", fillout below occultions:
kubectl [...] [...] deployment.v1.apps/kubernetes-bootcamp kubernetes-bootcamp= [...]
NOTE: the kubernetes-bootcamp= part is referring to the conatiner name (which you can get from "kubectl describe deployment kubernetes-bootcamp"
In kubernetes, let's say you have 4 pods, in deployment "kubernetes-bootcamp", that are running container image "gcr.io/google-sample/kubernetes-bootcamp:v1", issue command to do rolling upgrade to image "gcr.io/google-sample/kubernetes-bootcamp:v2", fillout below occultions:
kubectl [...] [...] deployment.v1.apps/kubernetes-bootcamp kubernetes-bootcamp= [...]
NOTE: the kubernetes-bootcamp= part is referring to the conatiner name (which you can get from "kubectl describe deployment kubernetes-bootcamp"
kubectl set image deployment.v1.apps/kubernetes-bootcamp kubernetes-bootcamp=gcr.io/google-sample/kubernetes-bootcamp:v2
| 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 |