OptionalamiOptionalamiChoose AMI type for the managed node group.
OptionaldesiredDesired size, defaults to min size.
Optional ReadonlydiskThe root device disk size (in GiB) for your node group instances.
Optional ReadonlyenableSpecifies whether to enable node auto repair for the node group. Node auto repair is disabled by default.
OptionalenableIf set to true will add AmazonSSMManagedInstanceCore to the node role.
Optional ReadonlyforceForce the update if the existing node group's pods are unable to be drained due to a pod disruption budget issue. If an update fails because pods could not be drained, you can force the update after it fails to terminate the old node whether or not any pods are running on the node.
Id of this node group. Expected to be unique in cluster scope.
OptionalinstanceInstance types used for the node group. Multiple types makes sense if capacity type is SPOT.
Optional ReadonlylabelsThe Kubernetes labels to be applied to the nodes in the node group when they are created.
OptionallaunchThe Launch Template properties for the Nodes.
amiType and amiReleaseVersion will be ignored if this is set.
Optional ReadonlylaunchLaunch template specification used for the nodegroup
OptionalmaxMax size of the node group.
Optional ReadonlymaxThe maximum number of nodes unavailable at once during a version update. Nodes will be updated in parallel. The maximum number is 100.
This value or maxUnavailablePercentage is required to have a value for custom update configurations to be applied.
Optional ReadonlymaxThe maximum percentage of nodes unavailable during a version update. This percentage of nodes will be updated in parallel, up to 100 nodes at once.
This value or maxUnavailable is required to have a value for custom update configurations to be applied.
OptionalminMin size of the node group
OptionalnodeSelect either SPOT or ON-DEMAND
Optional ReadonlynodegroupName of the Nodegroup
OptionalnodeSubnets for the autoscaling group where nodes (instances) will be placed.
Optional ReadonlynodeThe IAM role to associate with your node group. The Amazon EKS worker node kubelet daemon makes calls to AWS APIs on your behalf. Worker nodes receive permissions for these API calls through an IAM instance profile and associated policies. Before you can launch worker nodes and register them into a cluster, you must create an IAM role for those worker nodes to use when they are launched.
Optional ReadonlyremoteThe remote access (SSH) configuration to use with your node group. Disabled by default, however, if you specify an Amazon EC2 SSH key but do not specify a source security group when you create a managed node group, then port 22 on the worker nodes is opened to the internet (0.0.0.0/0)
Optional ReadonlytagsThe metadata to apply to the node group to assist with categorization and organization. Each tag consists of a key and an optional value, both of which you define. Node group tags do not propagate to any other resources associated with the node group, such as the Amazon EC2 instances or subnets.
Optional ReadonlytaintsThe Kubernetes taints to be applied to the nodes in the node group when they are created.
This property is used to upgrade node groups to the latest kubelet by upgrading node group AMI. Look up the versions here (mapped to Kubernetes version): https://docs.aws.amazon.com/eks/latest/userguide/eks-linux-ami-versions.html