whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix deployment.md with wrong READY numbers (#9584)

Browse Source 
The status of READY number should be 2 instead of 0, described
in the first line of table
This commit is contained in:
csskuber
2018-07-20 01:15:17 +08:00
committed by k8s-ci-robot
parent 427ac2a59c
commit 30e76b2781
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/workloads/controllers/deployment.md
+2 -2
View File
@@ -356,9 +356,9 @@ nginx-deployment-2035384211) and new replicas (nginx-deployment-3066724191) are
```shell ```shell
$ kubectl get rs $ kubectl get rs
NAME DESIRED CURRENT READY AGE NAME DESIRED CURRENT READY AGE
nginx-deployment-1564180365 2 2 0 25s nginx-deployment-1564180365 2 2 2 25s
nginx-deployment-2035384211 0 0 0 36s nginx-deployment-2035384211 0 0 0 36s
nginx-deployment-3066724191 2 2 2 6s nginx-deployment-3066724191 2 2 0 6s
``` ```
Looking at the Pods created, you will see that the 2 Pods created by new ReplicaSet are stuck in an image pull loop. Looking at the Pods created, you will see that the 2 Pods created by new ReplicaSet are stuck in an image pull loop.