From ee92eafd821ce8ece1156f52d93ebd6889f72faf Mon Sep 17 00:00:00 2001 From: wangxunbo Date: Wed, 31 May 2017 02:47:18 +0800 Subject: [PATCH] fix typo (#3895) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit I Created a deployment yaml file tomcatdp.yaml， and did not set the .spec.strategy，then run kubectl create -f tomcatdp.yaml, and then run kubectl get deployment tomcat-deployment -o yaml, the tomcat-deployment is the name of the deployment,found that the MaxUnavailable and MaxSurge default value is 25% --- docs/concepts/workloads/controllers/deployment.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/concepts/workloads/controllers/deployment.md b/docs/concepts/workloads/controllers/deployment.md index c91b8757b0..693c535ce3 100644 --- a/docs/concepts/workloads/controllers/deployment.md +++ b/docs/concepts/workloads/controllers/deployment.md @@ -823,7 +823,7 @@ the rolling update process. of Pods that can be unavailable during the update process. The value can be an absolute number (e.g. 5) or a percentage of desired Pods (e.g. 10%). The absolute number is calculated from percentage by rounding down. This can not be 0 if `.spec.strategy.rollingUpdate.maxSurge` is 0. By default, a -value of 1 is used. +value of 25% is used. For example, when this value is set to 30%, the old ReplicaSet can be scaled down to 70% of desired Pods immediately when the rolling update starts. Once new Pods are ready, old ReplicaSet can be scaled @@ -835,7 +835,7 @@ at all times during the update is at least 70% of the desired Pods. `.spec.strategy.rollingUpdate.maxSurge` is an optional field that specifies the maximum number of Pods that can be created above the desired number of Pods. Value can be an absolute number (e.g. 5) or a percentage of desired Pods (e.g. 10%). This can not be 0 if `MaxUnavailable` is 0. The absolute number -is calculated from percentage by rounding up. By default, a value of 1 is used. +is calculated from percentage by rounding up. By default, a value of 25% is used. For example, when this value is set to 30%, the new ReplicaSet can be scaled up immediately when the rolling update starts, such that the total number of old and new Pods do not exceed 130% of desired