From 4d029700cf9614d940dba53eb3b0a07d85b2d6e7 Mon Sep 17 00:00:00 2001 From: widearea101 <50230602+widearea101@users.noreply.github.com> Date: Tue, 24 Sep 2019 18:55:29 +0200 Subject: [PATCH] Update deployment.md (#16513) --- content/en/docs/concepts/workloads/controllers/deployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/controllers/deployment.md b/content/en/docs/concepts/workloads/controllers/deployment.md index dec61e6af3..60a6975de8 100644 --- a/content/en/docs/concepts/workloads/controllers/deployment.md +++ b/content/en/docs/concepts/workloads/controllers/deployment.md @@ -232,7 +232,7 @@ up to 3 replicas, as well as scaling down the old ReplicaSet to 0 replicas. it ensures that at least 75% of the desired number of Pods are up (25% max unavailable). Deployment also ensures that only a certain number of Pods are created above the desired number of Pods. - By default, it ensures that at most 25% of the desired number of Pods are up (25% max surge). + By default, it ensures that at most 125% of the desired number of Pods are up (25% max surge). For example, if you look at the above Deployment closely, you will see that it first created a new Pod, then deleted some old Pods, and created new ones. It does not kill old Pods until a sufficient number of