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

Resize google_container_cluster without destroying and re-creating #25

Closed
hashibot opened this issue Jun 13, 2017 · 1 comment · Fixed by #331
Closed

Resize google_container_cluster without destroying and re-creating #25

hashibot opened this issue Jun 13, 2017 · 1 comment · Fixed by #331
Assignees

Comments

@hashibot
Copy link

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


GKE supports resizing an underlying compute cluster on the fly:
https://cloud.google.com/container-engine/docs/resize-cluster

google_container_cluster's initial_node_count describes the initial count; if you change this the cluster is destroyed/re-created.

The docs describe getting at the underlying managed instance group gke-example-b937f2ba-node.

How can we do this in Terraform?

@danawillow danawillow self-assigned this Aug 9, 2017
luis-silva pushed a commit to luis-silva/terraform-provider-google that referenced this issue May 21, 2019
Make google_project_iam_policy authoritative.
@ghost
Copy link

ghost commented Mar 31, 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 👉 hashibot-feedback@hashicorp.com. Thanks!

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