You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hmm- looks like the fields are distinct. The top-level field applies when it's not a VPC-native cluster, and the nested field when the cluster is VPC-native.
The problem is, defining an ip_allocation_policy block at all makes the top-level field no longer work. So if the block is defined and you try to define a pod cidr, neither one will work. I'm not sure there's a remediation.
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 👉 hashibot-feedback@hashicorp.com. Thanks!
ghost
locked and limited conversation to collaborators
Nov 8, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I believe it's superseded by https://www.terraform.io/docs/providers/google/r/container_cluster.html#cluster_ipv4_cidr_block.
The text was updated successfully, but these errors were encountered: