-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Enable Non-RFC 1918 Addresses in 100.64.0.0/10 #6133
Comments
@spirrello do you have any pointers to docs that state this is possible in GCP today? https://cloud.google.com/vpc/docs/vpc#manually_created_subnet_ip_ranges and https://cloud.google.com/vpc/docs/using-vpc#subnet-rules both state that the subnet IP address needs to be RFC-1918. |
Hey @spirrello, I'm pretty sure this should work as-is as long as you're using the beta provider (since this is a beta feature). Can you give that a try and let me know? If you do try it and it doesn't work, would you mind showing me debug logs (the API request/response is all I need) from a failed run? |
FYI: documentation is here: https://cloud.google.com/architecture/configuring-privately-used-public-ips-for-GKE From a network point of view, it is now possible to add secondary ranges even if non RFC-1918 compliant (eg:1.1.0.0/23 for Pods on a GKE cluster). |
I'm going to close this as it appears to be working now. If you experience any issues, please feel free to open a new issue. Thanks! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Description
It would be great to allow for creating VPC subnets on the 100.64.0.0/10 (non-rfc 1918) address space. This is a private reserved address space that can be used for internal use cases.
Error message
New or Affected Resource(s)
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: