Optional
amiThis 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
Optional
amiChoose AMI type for the managed node group.
Optional
Readonly
clusterName for the cluster.
Optional
desiredDesired size, defaults to min size.
Optional
Readonly
diskThe root device disk size (in GiB) for your node group instances.
Optional
enableIf set to true will add AmazonSSMManagedInstanceCore to the node role.
Optional
Readonly
forceForce 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.
Optional
idIn this case id is optional and defaults tp the cluster name
Optional
instanceInstance types used for the node group. Multiple types makes sense if capacity type is SPOT.
Optional
isolatedIs the EKS Cluster in isolated subnets?
Optional
Readonly
labelsThe Kubernetes labels to be applied to the nodes in the node group when they are created.
Optional
launchThe Launch Template properties for the Nodes.
amiType
and amiReleaseVersion
will be ignored if this is set.
Optional
Readonly
launchLaunch template specification used for the nodegroup
Optional
maxMax size of the node group.
Optional
Readonly
maxThe 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
Readonly
maxThe 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.
Optional
minMin size of the node group
Optional
nameThe name for the cluster.
Optional
nodeSelect either SPOT or ON-DEMAND
Optional
Readonly
nodegroupName of the Nodegroup
Optional
nodeSubnets for the autoscaling group where nodes (instances) will be placed.
Optional
nodeTags for the node group.
Optional
Readonly
nodeThe 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
Readonly
outputDetermines whether a CloudFormation output with the name of the cluster will be synthesized.
Optional
Readonly
outputDetermines whether a CloudFormation output with the aws eks update-kubeconfig
command will be synthesized. This command will include
the cluster name and, if applicable, the ARN of the masters IAM role.
Optional
privateIs it a private only EKS Cluster? Defaults to private_and_public cluster, set to true for private cluster
Optional
Readonly
remoteThe 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
Readonly
roleRole that provides permissions for the Kubernetes control plane to make calls to AWS API operations on your behalf.
Optional
Readonly
securitySecurity Group to use for Control Plane ENIs
Optional
tagsTags for the Cluster.
Optional
Readonly
taintsThe Kubernetes taints to be applied to the nodes in the node group when they are created.
Optional
Readonly
versionThe Kubernetes version to run in the cluster
Optional
Readonly
vpcThe VPC in which to create the Cluster.
Optional
Readonly
vpcWhere to place EKS Control Plane ENIs
For example, to only select private subnets, supply the following:
vpcSubnets: [{ subnetType: ec2.SubnetType.PRIVATE_WITH_EGRESS }]
Configuration options for the cluster provider.