From b4f10b3874101fc003720ca1efccad011a42805b Mon Sep 17 00:00:00 2001 From: George Tseres Date: Wed, 24 Jul 2019 05:44:15 +0300 Subject: [PATCH] Fix field in PDB (#15480) --- content/en/docs/tasks/run-application/configure-pdb.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/run-application/configure-pdb.md b/content/en/docs/tasks/run-application/configure-pdb.md index 89ba99a4e8..c5c7417f42 100644 --- a/content/en/docs/tasks/run-application/configure-pdb.md +++ b/content/en/docs/tasks/run-application/configure-pdb.md @@ -86,7 +86,7 @@ Values for `minAvailable` or `maxUnavailable` can be expressed as integers or as - When you specify an integer, it represents a number of Pods. For instance, if you set `minAvailable` to 10, then 10 Pods must always be available, even during a disruption. - When you specify a percentage by setting the value to a string representation of a percentage (eg. `"50%"`), it represents a percentage of - total Pods. For instance, if you set `minUnavailable` to `"50%"`, then only 50% of the Pods can be unavailable during a + total Pods. For instance, if you set `maxUnavailable` to `"50%"`, then only 50% of the Pods can be unavailable during a disruption. When you specify the value as a percentage, it may not map to an exact number of Pods. For example, if you have 7 Pods and