eks: Add EKS Auto Mode support to Cluster L2 construct

[zjaco13]

Describe the feature

AWS Announced EKS Auto Mode on Dec 1st, enabling customers to fully automate cluster management for compute, storage, and networking. The CloudFormation changes for EKS Auto Mode enablement are adding a ComputeConfig field in the Cluster resource. Supporting this field would enable customers to easily create EKS Auto Mode or enable it on existing clusters.

Use Case

Create/Enable EKS Auto Mode on new or existing clusters for fully automated cluster management.

Proposed Solution

Add support for the ComputeConfig Field to the EKS Cluster L2 construct

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

CDK version used

2.171.1

Environment details (OS name and version, etc.)

mac OS Sonoma 14.7.1

[khushail]

Hi @zjaco13 , thanks for staying on top of the AWS cloudformation updates for EKS. Looks like its supported by cloudformation, so should be feasible to have support by CDK as well. Contributions are welcome.

[Issacwww]

@khushail
Is there any plan for L1 construct support? not seeing the ComputeConfig been added here
https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_eks.CfnCluster.html

[khushail]

@Issacwww , cloudformation docs mention about supporting this property-
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-eks-cluster-computeconfig.html

and in the resource specification doc, you can also see this as mentioned -

https://d1uauaxba7bl26.cloudfront.net/latest/gzip/CloudFormationResourceSpecification.json

Hopefully docs would reflect the latest changes in next cadence. Hope that helps!

[Issacwww]

Ah, Thanks for confirming, @khushail, makes sense if just doc delay, I will try the latest cdk version

[caleblloyd]

Is it possible to use an escape hatch to modify the L1 construct from the L2 construct for an EKS Cluster?

I am trying:

const cfnCluster = cluster.node.defaultChild as eks.CfnCluster
cfnCluster.computeConfig = {
  enabled: true,
  nodePools: ["system"],
  nodeRoleArn: nodeRole.roleArn,
}

But that is not working, maybe due to #18620. Is the eks.CfnCluster available under a different node than cluster.node.defaultChild?