-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Switch to cloud.json for cloud-netblocks #6996
Comments
Similar to the work done with Seems reasonable to do, I'll add the appropriate tag |
Since the IP addresses between the DNS record and the JSON file are different we have experienced some traffic being blocked unexpectedly. Just an FYI for anyone reading, you might want to hard code the IP ranges for the time being until this gets updated. |
in case anyone is looking for workaround this is what I've implemented on our side until the provider is fixed
and the helper script is slightly modified version of the script from doc at https://cloud.google.com/vpc/docs/configure-private-google-access#ip-addr-defaults
|
I have sent a PR to fix this #7157 |
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. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
From https://cloud.google.com/compute/docs/faq#find_ip_range
while the module is still querying the DNS record.
Maybe it would be better to switch to the JSON file as the documentation recommends.
The text was updated successfully, but these errors were encountered: