From 05f4c8ab7a472e44ad47e6a334010d4421875a25 Mon Sep 17 00:00:00 2001 From: Stewart-YU Date: Mon, 15 Oct 2018 15:44:13 +0800 Subject: [PATCH] Update deployment.md (#10615) fix the wrong comments --- .../workloads/controllers/deployment.md | 28 +++++++++---------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/content/en/docs/concepts/workloads/controllers/deployment.md b/content/en/docs/concepts/workloads/controllers/deployment.md index b8fbb7b9ca..8bc7f2f73b 100644 --- a/content/en/docs/concepts/workloads/controllers/deployment.md +++ b/content/en/docs/concepts/workloads/controllers/deployment.md @@ -172,14 +172,14 @@ instead of the `nginx:1.7.9` image. ```shell $ 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`: ```shell $ kubectl edit deployment/nginx-deployment -deployment.extensions/nginx-deployment edited +deployment.apps/nginx-deployment edited ``` To see the rollout status, run: @@ -187,7 +187,7 @@ To see the rollout status, run: ```shell $ kubectl rollout status deployment/nginx-deployment 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: @@ -338,7 +338,7 @@ Suppose that you made a typo while updating the Deployment, by putting the image ```shell $ 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. @@ -453,14 +453,14 @@ Now you've decided to undo the current rollout and rollback to the previous revi ```shell $ 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`: ```shell $ 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). @@ -532,7 +532,7 @@ Pods you want to run based on the CPU utilization of your existing Pods. ```shell $ kubectl autoscale deployment nginx-deployment --min=10 --max=15 --cpu-percent=80 -deployment.extensions/nginx-deployment scaled +deployment.apps/nginx-deployment scaled ``` ### Proportional scaling @@ -554,7 +554,7 @@ You update to a new image which happens to be unresolvable from inside the clust ```shell $ 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 @@ -608,14 +608,14 @@ Pause by running the following command: ```shell $ kubectl rollout pause deployment/nginx-deployment -deployment.extensions/nginx-deployment paused +deployment.apps/nginx-deployment paused ``` Then update the image of the Deployment: ```shell $ 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: @@ -635,7 +635,7 @@ You can make as many updates as you wish, for example, update the resources that ```shell $ 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 @@ -645,7 +645,7 @@ Eventually, resume the Deployment and observe a new ReplicaSet coming up with al ```shell $ kubectl rollout resume deploy/nginx-deployment -deployment.extensions/nginx-deployment resumed +deployment.apps/nginx-deployment resumed $ kubectl get rs -w NAME DESIRED CURRENT READY AGE nginx-2142116321 2 2 2 2m @@ -704,7 +704,7 @@ successfully, `kubectl rollout status` returns a zero exit code. ```shell $ kubectl rollout status deploy/nginx-deployment 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 $? 0 ``` @@ -731,7 +731,7 @@ lack of progress for a Deployment after 10 minutes: ```shell $ 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 attributes to the Deployment's `.status.conditions`: