-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Beta private cluster submodule does not support Dual stack networking #1656
Comments
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days |
This is being actively worked on in #1672. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days |
This is being actively worked on in #1672. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days |
TL;DR
The
beta-private-cluster
submodule lacks support for dual stack networking. It only propose to create a cluster in single stack mode, meaning IPv4 only.I'd like to introduce cluster with dual stack networking (IPv4/IPv6) as the
google_container_cluster
terraform resource is ready for Ipv4/IPv6. As such, pods will be addressed using IPv4 and IPv6 and Kubernetes Service will follow the same mechanism.Terraform Resources
The
ip_allocation_policy
map of thegoogle_container_cluster
terraform resource already propose the IPv6 stack activation as per the following documentationDetailed design
I could propose to introduce a new submodule variable
enable_ipv6
to activate the dual stack for both pods IP and Kubernetes Service IP.Additional information
No response
The text was updated successfully, but these errors were encountered: