placeholder documentation for maxUnavailable for StatefulSet
This commit is contained in:
@@ -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.
|
already attempted to run with the bad configuration.
|
||||||
StatefulSet will then begin to recreate the Pods using the reverted template.
|
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
|
## PersistentVolumeClaim retention
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user