From 29b1e2919e2de8923c665a13abce2ea256805801 Mon Sep 17 00:00:00 2001 From: csskuber Date: Thu, 19 Jul 2018 08:27:58 -0700 Subject: [PATCH] Fix deployment.md with wrong READY numbers The status of READY number should be 2 instead of 0, described in the first line of table --- content/en/docs/concepts/workloads/controllers/deployment.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/workloads/controllers/deployment.md b/content/en/docs/concepts/workloads/controllers/deployment.md index 92d7b67ddd321..6a616a1fab5a9 100644 --- a/content/en/docs/concepts/workloads/controllers/deployment.md +++ b/content/en/docs/concepts/workloads/controllers/deployment.md @@ -356,9 +356,9 @@ nginx-deployment-2035384211) and new replicas (nginx-deployment-3066724191) are ```shell $ kubectl get rs 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-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.