From 7f3f987c7659d3a677b31852fb94fc3f6d7f8780 Mon Sep 17 00:00:00 2001 From: Mayank Kumar Date: Thu, 5 Nov 2020 23:41:44 -0800 Subject: [PATCH] placeholder documentation for maxUnavailable for StatefulSet --- .../en/docs/concepts/workloads/controllers/statefulset.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/content/en/docs/concepts/workloads/controllers/statefulset.md b/content/en/docs/concepts/workloads/controllers/statefulset.md index 2ae481a431..04d74419f5 100644 --- a/content/en/docs/concepts/workloads/controllers/statefulset.md +++ b/content/en/docs/concepts/workloads/controllers/statefulset.md @@ -323,6 +323,11 @@ After reverting the template, you must also delete any Pods that StatefulSet had already attempted to run with the bad configuration. StatefulSet will then begin to recreate the Pods using the reverted template. +#### MaxUnavailable +The maximum number of pods that can be unavailable during the update. +Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). +Absolute number is calculated from percentage by rounding up. This can not be 0. +Defaults to 1. This field is alpha-level and is only honored by servers that enable the ## PersistentVolumeClaim retention