Update MaxUnavailableStatefulSet feature gate to beta

Signed-off-by: Heba Elayoty <heelayot@microsoft.com>

Kubernetes-commit: b656027b9363c4c6dbf4fa634a71d355abd99345
This commit is contained in:
Heba Elayoty
2025-07-23 10:52:55 -07:00
committed by Kubernetes Publisher
parent 5a42d726bf
commit 638e636503

View File

@@ -35,8 +35,7 @@ type RollingUpdateStatefulSetStrategyApplyConfiguration struct {
// 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
// MaxUnavailableStatefulSet feature. The field applies to all pods in the range 0 to
// Defaults to 1. This field is beta-level and is enabled by default. The field applies to all pods in the range 0 to
// Replicas-1. That means if there is any unavailable pod in the range 0 to Replicas-1, it
// will be counted towards MaxUnavailable.
MaxUnavailable *intstr.IntOrString `json:"maxUnavailable,omitempty"`