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
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment. If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.
When using VPC native with ip_allocation_policy I want to set a smaller cluster_secondary_range_name pod range. The default is /19. However from the Google doc link:
If you do not configure the maximum number of Pods per node, a /24 CIDR range is used, and each node is assigned 256 IP addresses.
Essentially that means we cannot take advantage of flexible pod cidr until we can change the max number of pods per node on the default node pool.
I actually have remove_default_node_pool = "true" set and use a google_container_node_pool resource with max_pods_per_node attribute set. But there is no way to currently stop or limit the default pool that gets deleted afterwards.
Status details
(1) deploy error: Not all instances running in IGM after 35m6.486038234s. Expect 1. Current errors: [IP_SPACE_EXHAUSTED]: Instance ‘xxxxx’ creation failed: IP space of ‘projects/xxxx/regions/australia-southeast1/subnetworks/xxxx’ is exhausted. - ; (2) deploy error: Not all instances running in IGM after 35m9.674823813s. Expect 1. Current errors: [IP_SPACE_EXHAUSTED]: Instance ‘xxxx’ creation failed: IP space of ‘projects/xxxx/regions/australia-southeast1/subnetworks/xxx’ is exhausted. - ; .
The text was updated successfully, but these errors were encountered:
bluemalkin
changed the title
google_container_cluster requires default-max-pods-per-node setting to support custom pod CIDR
google_container_cluster requires default-max-pods-per-node setting to support flexible pod CIDR
Jan 9, 2019
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
Feb 9, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Description
To take advantage of small CIDR for pod ranges currently in beta (https://cloud.google.com/kubernetes-engine/docs/how-to/flexible-pod-cidr), the maximum number of pods per node needs to be set-able for the
google_container_cluster
resource.When using VPC native with
ip_allocation_policy
I want to set a smallercluster_secondary_range_name
pod range. The default is/19
. However from the Google doc link:Essentially that means we cannot take advantage of flexible pod cidr until we can change the max number of pods per node on the default node pool.
I actually have
remove_default_node_pool = "true"
set and use agoogle_container_node_pool
resource withmax_pods_per_node
attribute set. But there is no way to currently stop or limit the default pool that gets deleted afterwards.New or Affected Resource(s)
Potential Terraform Configuration
Error
From the Google console:
The text was updated successfully, but these errors were encountered: