kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update deployment.md (#10615) 

fix the wrong comments
This commit is contained in:
Stewart-YU 2018-10-15 15:44:13 +08:00 committed by k8s-ci-robot
parent 34d06b1054
commit 05f4c8ab7a
1 changed files with 14 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
content/en/docs/concepts/workloads/controllers/deployment.md
View File

@ -172,14 +172,14 @@ instead of the `nginx:1.7.9` image.
```shell ```shell
$ kubectl set image deployment/nginx-deployment nginx=nginx:1.9.1 --record $ kubectl set image deployment/nginx-deployment nginx=nginx:1.9.1 --record
deployment.extensions/nginx-deployment image updated deployment.apps/nginx-deployment image updated
``` ```
Alternatively, you can `edit` the Deployment and change `.spec.template.spec.containers[0].image` from `nginx:1.7.9` to `nginx:1.9.1`: Alternatively, you can `edit` the Deployment and change `.spec.template.spec.containers[0].image` from `nginx:1.7.9` to `nginx:1.9.1`:
```shell ```shell
$ kubectl edit deployment/nginx-deployment $ kubectl edit deployment/nginx-deployment
deployment.extensions/nginx-deployment edited deployment.apps/nginx-deployment edited
``` ```
To see the rollout status, run: To see the rollout status, run:
@ -187,7 +187,7 @@ To see the rollout status, run:
```shell ```shell
$ kubectl rollout status deployment/nginx-deployment $ kubectl rollout status deployment/nginx-deployment
Waiting for rollout to finish: 2 out of 3 new replicas have been updated... Waiting for rollout to finish: 2 out of 3 new replicas have been updated...
deployment.extensions/nginx-deployment successfully rolled out deployment.apps/nginx-deployment successfully rolled out
``` ```
After the rollout succeeds, you may want to `get` the Deployment: After the rollout succeeds, you may want to `get` the Deployment:
@ -338,7 +338,7 @@ Suppose that you made a typo while updating the Deployment, by putting the image
```shell ```shell
$ kubectl set image deployment/nginx-deployment nginx=nginx:1.91 $ kubectl set image deployment/nginx-deployment nginx=nginx:1.91
deployment.extensions/nginx-deployment image updated deployment.apps/nginx-deployment image updated
``` ```
The rollout will be stuck. The rollout will be stuck.
@ -453,14 +453,14 @@ Now you've decided to undo the current rollout and rollback to the previous revi
```shell ```shell
$ kubectl rollout undo deployment/nginx-deployment $ kubectl rollout undo deployment/nginx-deployment
deployment.extensions/nginx-deployment deployment.apps/nginx-deployment
``` ```
Alternatively, you can rollback to a specific revision by specify that in `--to-revision`: Alternatively, you can rollback to a specific revision by specify that in `--to-revision`:
```shell ```shell
$ kubectl rollout undo deployment/nginx-deployment --to-revision=2 $ kubectl rollout undo deployment/nginx-deployment --to-revision=2
deployment.extensions/nginx-deployment deployment.apps/nginx-deployment
``` ```
For more details about rollout related commands, read [`kubectl rollout`](/docs/reference/generated/kubectl/kubectl-commands#rollout). For more details about rollout related commands, read [`kubectl rollout`](/docs/reference/generated/kubectl/kubectl-commands#rollout).
@ -532,7 +532,7 @@ Pods you want to run based on the CPU utilization of your existing Pods.
```shell ```shell
$ kubectl autoscale deployment nginx-deployment --min=10 --max=15 --cpu-percent=80 $ kubectl autoscale deployment nginx-deployment --min=10 --max=15 --cpu-percent=80
deployment.extensions/nginx-deployment scaled deployment.apps/nginx-deployment scaled
``` ```
### Proportional scaling ### Proportional scaling
@ -554,7 +554,7 @@ You update to a new image which happens to be unresolvable from inside the clust
```shell ```shell
$ kubectl set image deploy/nginx-deployment nginx=nginx:sometag $ kubectl set image deploy/nginx-deployment nginx=nginx:sometag
deployment.extensions/nginx-deployment image updated deployment.apps/nginx-deployment image updated
``` ```
The image update starts a new rollout with ReplicaSet nginx-deployment-1989198191, but it's blocked due to the The image update starts a new rollout with ReplicaSet nginx-deployment-1989198191, but it's blocked due to the
@ -608,14 +608,14 @@ Pause by running the following command:
```shell ```shell
$ kubectl rollout pause deployment/nginx-deployment $ kubectl rollout pause deployment/nginx-deployment
deployment.extensions/nginx-deployment paused deployment.apps/nginx-deployment paused
``` ```
Then update the image of the Deployment: Then update the image of the Deployment:
```shell ```shell
$ kubectl set image deploy/nginx-deployment nginx=nginx:1.9.1 $ kubectl set image deploy/nginx-deployment nginx=nginx:1.9.1
deployment.extensions/nginx-deployment image updated deployment.apps/nginx-deployment image updated
``` ```
Notice that no new rollout started: Notice that no new rollout started:
@ -635,7 +635,7 @@ You can make as many updates as you wish, for example, update the resources that
```shell ```shell
$ kubectl set resources deployment nginx-deployment -c=nginx --limits=cpu=200m,memory=512Mi $ kubectl set resources deployment nginx-deployment -c=nginx --limits=cpu=200m,memory=512Mi
deployment.extensions/nginx-deployment resource requirements updated deployment.apps/nginx-deployment resource requirements updated
``` ```
The initial state of the Deployment prior to pausing it will continue its function, but new updates to The initial state of the Deployment prior to pausing it will continue its function, but new updates to
@ -645,7 +645,7 @@ Eventually, resume the Deployment and observe a new ReplicaSet coming up with al
```shell ```shell
$ kubectl rollout resume deploy/nginx-deployment $ kubectl rollout resume deploy/nginx-deployment
deployment.extensions/nginx-deployment resumed deployment.apps/nginx-deployment resumed
$ kubectl get rs -w $ kubectl get rs -w
NAME DESIRED CURRENT READY AGE NAME DESIRED CURRENT READY AGE
nginx-2142116321 2 2 2 2m nginx-2142116321 2 2 2 2m
@ -704,7 +704,7 @@ successfully, `kubectl rollout status` returns a zero exit code.
```shell ```shell
$ kubectl rollout status deploy/nginx-deployment $ kubectl rollout status deploy/nginx-deployment
Waiting for rollout to finish: 2 of 3 updated replicas are available... Waiting for rollout to finish: 2 of 3 updated replicas are available...
deployment.extensions/nginx-deployment successfully rolled out deployment.apps/nginx-deployment successfully rolled out
$ echo $? $ echo $?
0 0
``` ```
@ -731,7 +731,7 @@ lack of progress for a Deployment after 10 minutes:
```shell ```shell
$ kubectl patch deployment/nginx-deployment -p '{"spec":{"progressDeadlineSeconds":600}}' $ kubectl patch deployment/nginx-deployment -p '{"spec":{"progressDeadlineSeconds":600}}'
deployment.extensions/nginx-deployment patched deployment.apps/nginx-deployment patched
``` ```
Once the deadline has been exceeded, the Deployment controller adds a DeploymentCondition with the following Once the deadline has been exceeded, the Deployment controller adds a DeploymentCondition with the following
attributes to the Deployment's `.status.conditions`: attributes to the Deployment's `.status.conditions`: