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.

@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

@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!

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

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?

Requires JavaScript SDK >= 3.703.0 and latest CloudFormation schema

This issue has received a significant amount of attention so we are automatically upgrading its priority. A member of the community will see the re-prioritization and provide an update on the issue.