From 93e241a0017150d02e2be7ed2a5769b55d050395 Mon Sep 17 00:00:00 2001 From: Manish Bansal Date: Fri, 6 Dec 2019 16:48:50 +0530 Subject: [PATCH] Document correction for PDB (#17573) * Document correction for PDB The word "may" should be replaced with "will". I do not see any reason for the ambiguity here. * Updated as per review comments * Updated as per review comments --- content/en/docs/tasks/run-application/configure-pdb.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/content/en/docs/tasks/run-application/configure-pdb.md b/content/en/docs/tasks/run-application/configure-pdb.md index a53558d45e..673823feb7 100644 --- a/content/en/docs/tasks/run-application/configure-pdb.md +++ b/content/en/docs/tasks/run-application/configure-pdb.md @@ -144,8 +144,10 @@ collection below the specified size. The budget can only protect against voluntary evictions, not all causes of unavailability. {{< /note >}} -A `maxUnavailable` of 0% (or 0) or a `minAvailable` of 100% (or equal to the -number of replicas) may block node drains entirely. This is permitted as per the +If you set `maxUnavailable` to 0% or 0, or you set `minAvailable` to 100% or the number of replicas, +you are requiring zero voluntary evictions. When you set zero voluntary evictions for a workload +object such as ReplicaSet, then you cannot successfully drain a Node running one of those Pods. +If you try to drain a Node where an unevictable Pod is running, the drain never completes. This is permitted as per the semantics of `PodDisruptionBudget`. You can find examples of pod disruption budgets defined below. They match pods with the label