aws-cdk-lib.aws_eks_v2.CfnNodegroup.UpdateConfigProperty

UpdateConfigProperty Struct

The update configuration for the node group.

Source

Generated code

Type last changed

v2.268.0 · 2 Sep 2026

Example

// The code below shows an example of how to instantiate this type.
// The values are placeholders you should change.
import { aws_eks_v2 as eks_v2 } from 'aws-cdk-lib';
const updateConfigProperty: eks_v2.CfnNodegroup.UpdateConfigProperty = {
  maxUnavailable: 123,
  maxUnavailablePercentage: 123,
  updateStrategy: 'updateStrategy',
};

Properties

maxUnavailable?optionalnumbermax_unavailable?optionalint | floatmaxUnavailable?optionalNumberMaxUnavailable?optionaldoubleMaxUnavailable?optional*float64#

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.

maxUnavailablePercentage?optionalnumbermax_unavailable_percentage?optionalint | floatmaxUnavailablePercentage?optionalNumberMaxUnavailablePercentage?optionaldoubleMaxUnavailablePercentage?optional*float64#

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.

updateStrategy?optionalstringupdate_strategy?optionalstrupdateStrategy?optionalStringUpdateStrategy?optionalstringUpdateStrategy?optional*string#

The configuration for the behavior to follow during a node group version update of this managed node group.

notes

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).