rollingUpdate
Rolling update options. Only valid when strategy is RollingUpdate. Both the shorthand keys (surge/unavailable) and the upstream Kubernetes keys (maxSurge/maxUnavailable) are accepted. When both are set, the Kubernetes key takes priority. The shorthand keys are deprecated and Will be removed in v6.0.
object
Properties
Section titled “Properties”| Property | Type | Required | Default | Description |
|---|---|---|---|---|
maxSurge | integer / string | No | - | Maximum number of pods that can be created over the desir… |
maxUnavailable | integer / string | No | - | Maximum number of pods that can be unavailable during the… |
surge | integer / string | No | - | Deprecated: use maxSurge instead. Will be removed in v6… |
unavailable | integer / string | No | - | Deprecated: use maxUnavailable instead. Will be removed… |
Property Details
Section titled “Property Details”maxSurge
Section titled “maxSurge”Maximum number of pods that can be created over the desired replicas during the update.
maxUnavailable
Section titled “maxUnavailable”Maximum number of pods that can be unavailable during the update.
Deprecated: use maxSurge instead. Will be removed in v6.0. Maximum number of pods that can be created over the desired replicas during the update.
unavailable
Section titled “unavailable”Deprecated: use maxUnavailable instead. Will be removed in v6.0. Maximum number of pods that can be unavailable during the update.