-
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
Support for node pool surge upgrades #4841
Comments
This is already available on instance group templates:
So probably best to follow the same structure? |
@Stono the PR addressing this issue is here: GoogleCloudPlatform/magic-modules#2669 |
GoogleCloudPlatform/magic-modules#2669 was merged today and should be available in 3.1.0. |
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
Google has introduced a new feature for nodepool upgrades - it's called "surge upgrade".
New or Affected Resource(s)
Potential Terraform Configuration
This feature is controlled by two distinct parameters, and there should be provision to support these:
References
Feature is described here: https://cloud.google.com/kubernetes-engine/docs/concepts/cluster-upgrades#surge
The text was updated successfully, but these errors were encountered: