Skip to content
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

Closed
gillesdouaire opened this issue Nov 8, 2019 · 4 comments
Closed

Support for node pool surge upgrades #4841

gillesdouaire opened this issue Nov 8, 2019 · 4 comments

Comments

@gillesdouaire
Copy link

gillesdouaire commented Nov 8, 2019

Community Note

  • 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.

Description

Google has introduced a new feature for nodepool upgrades - it's called "surge upgrade".

New or Affected Resource(s)

  • google_container_node_pool

Potential Terraform Configuration

This feature is controlled by two distinct parameters, and there should be provision to support these:

  • max-surge-upgrade
  • max-unavailable-upgrade

References

Feature is described here: https://cloud.google.com/kubernetes-engine/docs/concepts/cluster-upgrades#surge

@ghost ghost added the enhancement label Nov 8, 2019
@Stono
Copy link

Stono commented Nov 12, 2019

This is already available on instance group templates:

      + update_policy {
          + max_surge_fixed       = 0
          + max_unavailable_fixed = 1
          + min_ready_sec         = 0
          + minimal_action        = "REPLACE"
          + type                  = "PROACTIVE"
        }

So probably best to follow the same structure?

@chrissng
Copy link
Contributor

@Stono the google_container_node_pool underlying GKE Beta API specifies only two settings: https://cloud.google.com/kubernetes-engine/docs/reference/rest/v1beta1/UpgradeSettings

PR addressing this issue is here: GoogleCloudPlatform/magic-modules#2669

@danawillow
Copy link
Contributor

GoogleCloudPlatform/magic-modules#2669 was merged today and should be available in 3.1.0.

@ghost
Copy link

ghost commented Mar 28, 2020

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!

@ghost ghost locked and limited conversation to collaborators Mar 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants