Interface NodegroupUpdateConfig.Builder
-
- All Superinterfaces:
Buildable,CopyableBuilder<NodegroupUpdateConfig.Builder,NodegroupUpdateConfig>,SdkBuilder<NodegroupUpdateConfig.Builder,NodegroupUpdateConfig>,SdkPojo
- Enclosing class:
- NodegroupUpdateConfig
public static interface NodegroupUpdateConfig.Builder extends SdkPojo, CopyableBuilder<NodegroupUpdateConfig.Builder,NodegroupUpdateConfig>
-
-
Method Summary
All Methods Instance Methods Abstract Methods Modifier and Type Method Description NodegroupUpdateConfig.BuildermaxUnavailable(Integer maxUnavailable)The maximum number of nodes unavailable at once during a version update.NodegroupUpdateConfig.BuildermaxUnavailablePercentage(Integer maxUnavailablePercentage)The maximum percentage of nodes unavailable during a version update.NodegroupUpdateConfig.BuilderupdateStrategy(String updateStrategy)The configuration for the behavior to follow during a node group version update of this managed node group.NodegroupUpdateConfig.BuilderupdateStrategy(NodegroupUpdateStrategies updateStrategy)The configuration for the behavior to follow during a node group version update of this managed node group.-
Methods inherited from interface software.amazon.awssdk.utils.builder.CopyableBuilder
copy
-
Methods inherited from interface software.amazon.awssdk.utils.builder.SdkBuilder
applyMutation, build
-
Methods inherited from interface software.amazon.awssdk.core.SdkPojo
equalsBySdkFields, sdkFieldNameToField, sdkFields
-
-
-
-
Method Detail
-
maxUnavailable
NodegroupUpdateConfig.Builder maxUnavailable(Integer maxUnavailable)
The maximum number of nodes unavailable at once during a version update. Nodes are updated in parallel. This value or
maxUnavailablePercentageis required to have a value.The maximum number is 100.- Parameters:
maxUnavailable- The maximum number of nodes unavailable at once during a version update. Nodes are updated in parallel. This value ormaxUnavailablePercentageis required to have a value.The maximum number is 100.- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
maxUnavailablePercentage
NodegroupUpdateConfig.Builder maxUnavailablePercentage(Integer maxUnavailablePercentage)
The maximum percentage of nodes unavailable during a version update. This percentage of nodes are updated in parallel, up to 100 nodes at once. This value or
maxUnavailableis required to have a value.- Parameters:
maxUnavailablePercentage- The maximum percentage of nodes unavailable during a version update. This percentage of nodes are updated in parallel, up to 100 nodes at once. This value ormaxUnavailableis required to have a value.- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
updateStrategy
NodegroupUpdateConfig.Builder updateStrategy(String updateStrategy)
The configuration for the behavior to follow during a node group version update of this managed node group. You choose between two possible strategies for replacing nodes during an
UpdateNodegroupVersionaction.An Amazon EKS managed node group updates by replacing nodes with new nodes of newer AMI versions in parallel. The update strategy changes the managed node update behavior of the managed node group for each quantity. The default strategy has guardrails to protect you from misconfiguration and launches the new instances first, before terminating the old instances. The minimal strategy removes the guardrails and terminates the old instances before launching the new instances. This minimal strategy is useful in scenarios where you are constrained to resources or costs (for example, with hardware accelerators such as GPUs).
- Parameters:
updateStrategy- The configuration for the behavior to follow during a node group version update of this managed node group. You choose between two possible strategies for replacing nodes during anUpdateNodegroupVersionaction.An Amazon EKS managed node group updates by replacing nodes with new nodes of newer AMI versions in parallel. The update strategy changes the managed node update behavior of the managed node group for each quantity. The default strategy has guardrails to protect you from misconfiguration and launches the new instances first, before terminating the old instances. The minimal strategy removes the guardrails and terminates the old instances before launching the new instances. This minimal strategy is useful in scenarios where you are constrained to resources or costs (for example, with hardware accelerators such as GPUs).
- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
NodegroupUpdateStrategies,NodegroupUpdateStrategies
-
updateStrategy
NodegroupUpdateConfig.Builder updateStrategy(NodegroupUpdateStrategies updateStrategy)
The configuration for the behavior to follow during a node group version update of this managed node group. You choose between two possible strategies for replacing nodes during an
UpdateNodegroupVersionaction.An Amazon EKS managed node group updates by replacing nodes with new nodes of newer AMI versions in parallel. The update strategy changes the managed node update behavior of the managed node group for each quantity. The default strategy has guardrails to protect you from misconfiguration and launches the new instances first, before terminating the old instances. The minimal strategy removes the guardrails and terminates the old instances before launching the new instances. This minimal strategy is useful in scenarios where you are constrained to resources or costs (for example, with hardware accelerators such as GPUs).
- Parameters:
updateStrategy- The configuration for the behavior to follow during a node group version update of this managed node group. You choose between two possible strategies for replacing nodes during anUpdateNodegroupVersionaction.An Amazon EKS managed node group updates by replacing nodes with new nodes of newer AMI versions in parallel. The update strategy changes the managed node update behavior of the managed node group for each quantity. The default strategy has guardrails to protect you from misconfiguration and launches the new instances first, before terminating the old instances. The minimal strategy removes the guardrails and terminates the old instances before launching the new instances. This minimal strategy is useful in scenarios where you are constrained to resources or costs (for example, with hardware accelerators such as GPUs).
- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
NodegroupUpdateStrategies,NodegroupUpdateStrategies
-
-