Interface DeploymentStrategyRollingUpdateOptions
-
- All Superinterfaces:
software.amazon.jsii.JsiiSerializable
- All Known Implementing Classes:
DeploymentStrategyRollingUpdateOptions.Jsii$Proxy
@Generated(value="jsii-pacmak/1.72.0 (build 4b8828b)", date="2022-12-22T02:29:49.484Z") @Stability(Stable) public interface DeploymentStrategyRollingUpdateOptions extends software.amazon.jsii.JsiiSerializable
Options for `DeploymentStrategy.rollingUpdate`.
-
-
Nested Class Summary
Nested Classes Modifier and Type Interface Description static class
DeploymentStrategyRollingUpdateOptions.Builder
A builder forDeploymentStrategyRollingUpdateOptions
static class
DeploymentStrategyRollingUpdateOptions.Jsii$Proxy
An implementation forDeploymentStrategyRollingUpdateOptions
-
Method Summary
All Methods Static Methods Instance Methods Default Methods Modifier and Type Method Description static DeploymentStrategyRollingUpdateOptions.Builder
builder()
default PercentOrAbsolute
getMaxSurge()
The maximum number of pods that can be scheduled above the desired number of pods.default PercentOrAbsolute
getMaxUnavailable()
The maximum number of pods that can be unavailable during the update.
-
-
-
Method Detail
-
getMaxSurge
@Stability(Stable) @Nullable default PercentOrAbsolute getMaxSurge()
The maximum number of pods that can be scheduled above the desired number of pods.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 if
maxUnavailable
is 0.Example: when this is set to 30%, the new ReplicaSet can be scaled up immediately when the rolling update starts, such that the total number of old and new pods do not exceed 130% of desired pods. Once old pods have been killed, new ReplicaSet can be scaled up further, ensuring that total number of pods running at any time during the update is at most 130% of desired pods.
Default: '25%'
-
getMaxUnavailable
@Stability(Stable) @Nullable default PercentOrAbsolute getMaxUnavailable()
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 down. This can not be 0 if
maxSurge
is 0.Example: when this is set to 30%, the old ReplicaSet can be scaled down to 70% of desired pods immediately when the rolling update starts. Once new pods are ready, old ReplicaSet can be scaled down further, followed by scaling up the new ReplicaSet, ensuring that the total number of pods available at all times during the update is at least 70% of desired pods.
Default: '25%'
-
builder
@Stability(Stable) static DeploymentStrategyRollingUpdateOptions.Builder builder()
-
-