/AWS1/CL_EKSNODEGROUPUPDATECFG¶
The node group update configuration. An Amazon EKS managed node group updates by replacing nodes with new nodes of newer AMI versions in parallel. You choose the maximum unavailable and the update strategy.
CONSTRUCTOR
¶
IMPORTING¶
Optional arguments:¶
iv_maxunavailable
TYPE /AWS1/EKSNONZEROINTEGER
/AWS1/EKSNONZEROINTEGER
¶
The maximum number of nodes unavailable at once during a version update. Nodes are updated in parallel. This value or
maxUnavailablePercentage
is required to have a value.The maximum number is 100.
iv_maxunavailablepercentage
TYPE /AWS1/EKSPERCENTCAPACITY
/AWS1/EKSPERCENTCAPACITY
¶
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
maxUnavailable
is required to have a value.
iv_updatestrategy
TYPE /AWS1/EKSNODEGRPUPDSTRATEGIES
/AWS1/EKSNODEGRPUPDSTRATEGIES
¶
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
UpdateNodegroupVersion
action.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).
Queryable Attributes¶
maxUnavailable¶
The maximum number of nodes unavailable at once during a version update. Nodes are updated in parallel. This value or
maxUnavailablePercentage
is required to have a value.The maximum number is 100.
Accessible with the following methods¶
Method | Description |
---|---|
GET_MAXUNAVAILABLE() |
Getter for MAXUNAVAILABLE, with configurable default |
ASK_MAXUNAVAILABLE() |
Getter for MAXUNAVAILABLE w/ exceptions if field has no valu |
HAS_MAXUNAVAILABLE() |
Determine if MAXUNAVAILABLE has a value |
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
maxUnavailable
is required to have a value.
Accessible with the following methods¶
Method | Description |
---|---|
GET_MAXUNAVAILABLEPERCENTAGE() |
Getter for MAXUNAVAILABLEPERCENTAGE, with configurable defau |
ASK_MAXUNAVAILABLEPERCENTAGE() |
Getter for MAXUNAVAILABLEPERCENTAGE w/ exceptions if field h |
HAS_MAXUNAVAILABLEPERCENTAGE() |
Determine if MAXUNAVAILABLEPERCENTAGE has a value |
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
UpdateNodegroupVersion
action.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).
Accessible with the following methods¶
Method | Description |
---|---|
GET_UPDATESTRATEGY() |
Getter for UPDATESTRATEGY, with configurable default |
ASK_UPDATESTRATEGY() |
Getter for UPDATESTRATEGY w/ exceptions if field has no valu |
HAS_UPDATESTRATEGY() |
Determine if UPDATESTRATEGY has a value |