[FEAT] Enable IPv6 EKS Clusters

[RyanDevlin]

Describe the feature

There are older feature requests to enable IPv6 clusters with EKS Blueprints, but it looks they were closed due to lack of CDK support.

The CDK team has now enabled this feature, and I think it should be supported in EKS Blueprints as well.

Use Case

I work for an internal AWS team and we have a very strong use-case for IPv6 clusters built via EKS Blueprints. I can explain more about my team's use-case over internal Slack messages, but also many external customers can benefit from this feature as it avoids complex IPv4 CIDR management when running large-scale clusters.

Proposed Solution

This change should be relatively easy to make up front, as we simply need to pipe through a new configuration enum called ipFamily which can be set to ipv4 or ipv6. We then just pass that to our existing call to eks.createCluster().

The hard part would be validating the EKS AddOns all support ipv6, and if not, raising incompatibility errors for AddOns which are not compatible or handling this some other way.

Other Information

A list of IPv6 compatibilities and considerations: https://docs.aws.amazon.com/eks/latest/userguide/cni-ipv6.html#ipv6-considerations.

Acknowledgements

• [ ] I may be able to implement this feature request

CDK version used

2.115.0

EKS Blueprints Version

1.13.1

Node.js Version

^14.18.13

Environment details (OS name and version, etc.)

AL2 for deploying CDK, bottlerocket hosts within the EKS cluster.

[elamaran11]

@RyanDevlin Thankyou for the issue, we will prioritize that at some point soon.

[github-actions[bot]]

This issue has been automatically marked as stale because it has been open 60 days with no activity. Remove stale label or comment or this issue will be closed in 10 days

[elamaran11]

@bugathagit Hope you are helping us on this.

[bugathagit]

@elamaran11 Yes, I am working on this.