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

providers/google: Support for Node Auto-Repair in google_container_cluster (GKE) #80

Closed
hashibot opened this issue Jun 13, 2017 · 7 comments

Comments

@hashibot
Copy link

This issue was originally opened by @cblecker as hashicorp/terraform#13392. It was migrated here as part of the provider split. The original body of the issue is below.


Relates to #44

Requesting support for node auto-repair on GKE clusters: https://cloud.google.com/container-engine/docs/node-auto-repair

cc: @danawillow @paddyforan

@stonith
Copy link

stonith commented Jun 28, 2017

Also add to google_container_node_pool resource.

@danawillow
Copy link
Contributor

Thanks! Linking to #93 so we can easily keep track of all the beta FRs.

@danawillow
Copy link
Contributor

Fixed in #669

@leg100
Copy link

leg100 commented Dec 13, 2017

@danawillow this issue is requesting support for auto_repair on the google_container_cluster resource (which I take to mean on its default node pool). Doesn't #669 add support for it on the google_container_node_pool resource only?

@tpoindessous
Copy link
Contributor

Hi @danawillow

I agree with @leg100, I can't find the way to specify node auto_repair when using google_container_cluster resource.

Thanks in advance.

@pdecat
Copy link
Contributor

pdecat commented Jun 20, 2018

Here's a snippet of how to do it:

resource "google_container_cluster" "gke_cluster" {
  name       = "mycluster"
  zone       = "europe-west1-b"

  node_pool {
    name = "mypool"

    management {
      auto_repair  = true
      auto_upgrade = false
    }
[...]

@ghost
Copy link

ghost commented Nov 17, 2018

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 Nov 17, 2018
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

6 participants