site: Update tutorial images
parent
24520428d5
commit
b02c349ed3
|
@ -33,7 +33,7 @@ Here we see the available nodes (1 in our case). Kubernetes will choose where to
|
|||
Let's deploy our first app on Kubernetes with the `kubectl create deployment` command. We need to provide the deployment name and app image location (include the full repository url for images hosted outside Docker Hub).
|
||||
|
||||
```shell
|
||||
kubectl create deployment kubernetes-bootcamp --image=gcr.io/google-samples/kubernetes-bootcamp:v1
|
||||
kubectl create deployment kubernetes-bootcamp --image=gcr.io/k8s-minikube/kubernetes-bootcamp:v1
|
||||
```
|
||||
|
||||
Great! You just deployed your first application by creating a deployment. This performed a few things for you:
|
||||
|
|
|
@ -31,7 +31,7 @@ kubectl describe pods
|
|||
To update the image of the application to version 2, use the `set image` command, followed by the deployment name and the new image version:
|
||||
|
||||
```shell
|
||||
kubectl set image deployments/kubernetes-bootcamp kubernetes-bootcamp=jocatalin/kubernetes-bootcamp:v2
|
||||
kubectl set image deployments/kubernetes-bootcamp kubernetes-bootcamp=gcr.io/k8s-minikube/kubernetes-bootcamp:v2
|
||||
```
|
||||
|
||||
The command notified the Deployment to use a different image for your app and initiated a rolling update. Check the status of the new Pods, and view the old one terminating with the `get pods` command:
|
||||
|
@ -85,7 +85,7 @@ In the `Image` field of the output, verify that you are running the latest image
|
|||
Let's perform another update, and deploy an image tagged with `v10`:
|
||||
|
||||
```shell
|
||||
kubectl set image deployments/kubernetes-bootcamp kubernetes-bootcamp=gcr.io/google-samples/kubernetes-bootcamp:v10
|
||||
kubectl set image deployments/kubernetes-bootcamp kubernetes-bootcamp=gcr.io/k8s-minikube/kubernetes-bootcamp:v10
|
||||
```
|
||||
|
||||
Use `get deployments` to see the status of the deployment:
|
||||
|
|
Loading…
Reference in New Issue