-
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
Add support for MaxPodsConstraint in GKE #2023
Comments
Oh, cool, yesterday they regenerated the client libraries to contain this method, and this is doable now. :) |
If not set, does this default to zero? |
Yep! My understanding is that on the server side it defaults to "unset", which means no limit, and that sending a zero doesn't change that. There's some confusion on that point, though - to help, we've just merged a change that makes the field |
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! |
Community Note
Description
The cluster API now contains a field in beta to control the maximum number of pods per node. This changes the kubelet's
--max-pods
parameter, as well as the size of the subnet allocated to a node in Alias IP mode.New or Affected Resource(s)
google_container_cluster
google_container_node_pool
Potential Terraform Configuration
Note
The API documentation is still missing this field for some reason, but the API reference has it already, as well as the CLI cluster creation reference, and node pool creation reference.
The text was updated successfully, but these errors were encountered: