Remove the unessary code type

According to the rest part of this article. the `shell` for the output of command might be omitted
This commit is contained in:
lostsquirrel 2020-08-20 16:16:36 +08:00 committed by GitHub
parent 3c0c8b72ef
commit fdade94ecb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions

View File

@ -84,7 +84,7 @@ Follow the steps given below to create the above Deployment:
2. Run `kubectl get deployments` to check if the Deployment was created. 2. Run `kubectl get deployments` to check if the Deployment was created.
If the Deployment is still being created, the output is similar to the following: If the Deployment is still being created, the output is similar to the following:
```shell ```
NAME READY UP-TO-DATE AVAILABLE AGE NAME READY UP-TO-DATE AVAILABLE AGE
nginx-deployment 0/3 0 0 1s nginx-deployment 0/3 0 0 1s
``` ```
@ -100,21 +100,21 @@ Follow the steps given below to create the above Deployment:
3. To see the Deployment rollout status, run `kubectl rollout status deployment.v1.apps/nginx-deployment`. 3. To see the Deployment rollout status, run `kubectl rollout status deployment.v1.apps/nginx-deployment`.
The output is similar to: The output is similar to:
```shell ```
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.apps/nginx-deployment successfully rolled out deployment.apps/nginx-deployment successfully rolled out
``` ```
4. Run the `kubectl get deployments` again a few seconds later. 4. Run the `kubectl get deployments` again a few seconds later.
The output is similar to this: The output is similar to this:
```shell ```
NAME READY UP-TO-DATE AVAILABLE AGE NAME READY UP-TO-DATE AVAILABLE AGE
nginx-deployment 3/3 3 3 18s nginx-deployment 3/3 3 3 18s
``` ```
Notice that the Deployment has created all three replicas, and all replicas are up-to-date (they contain the latest Pod template) and available. Notice that the Deployment has created all three replicas, and all replicas are up-to-date (they contain the latest Pod template) and available.
5. To see the ReplicaSet (`rs`) created by the Deployment, run `kubectl get rs`. The output is similar to this: 5. To see the ReplicaSet (`rs`) created by the Deployment, run `kubectl get rs`. The output is similar to this:
```shell ```
NAME DESIRED CURRENT READY AGE NAME DESIRED CURRENT READY AGE
nginx-deployment-75675f5897 3 3 3 18s nginx-deployment-75675f5897 3 3 3 18s
``` ```
@ -131,7 +131,7 @@ Follow the steps given below to create the above Deployment:
6. To see the labels automatically generated for each Pod, run `kubectl get pods --show-labels`. 6. To see the labels automatically generated for each Pod, run `kubectl get pods --show-labels`.
The output is similar to: The output is similar to:
```shell ```
NAME READY STATUS RESTARTS AGE LABELS NAME READY STATUS RESTARTS AGE LABELS
nginx-deployment-75675f5897-7ci7o 1/1 Running 0 18s app=nginx,pod-template-hash=3123191453 nginx-deployment-75675f5897-7ci7o 1/1 Running 0 18s app=nginx,pod-template-hash=3123191453
nginx-deployment-75675f5897-kzszj 1/1 Running 0 18s app=nginx,pod-template-hash=3123191453 nginx-deployment-75675f5897-kzszj 1/1 Running 0 18s app=nginx,pod-template-hash=3123191453