-
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
Autoscaling in combination with node_count for google_container_cluster #844
Comments
Confirmation that using 'initital_node_count' fixes the issue, but since that one is deprecated, I would like some advice on how to setup this config :-) |
Question- if you set autoscaling but not node_count, what would you expect to happen? It seems like we have two options:
I like the second one so that users don't have to worry about whether they set initial_node_count or node_count for their node pools (in case they add autoscaling later, for example), but I also only want to do that if it doesn't lead to unexpected behavior. |
I like the second one best as well. |
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! |
Hi there,
Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.
Terraform Version
Affected Resource(s)
Please list the resources as a list, for example:
Terraform Configuration Files
Debug Output
See https://gist.github.com/wmuizelaar/b32116014ac72767b9dd26e6e585b5e1
Expected Behavior
Nothing should have happened, since the node_count change should be ignore due to the lifecycle configuration.
Actual Behavior
The nodecount was changed, and therefore the current node-count will be decreased to 1 again.
Steps to Reproduce
terraform apply
terraform apply
again. TheImportant Factoids
I would think that the initial_node_count could be used to 'fix' this issue, but that option is deprecated. So maybe I'm doing things wrong, but if I create a cluster without the node_count parameter, the cluster-size gets set to '0', and auto-scaling doesn't scale it up to '1'.
The text was updated successfully, but these errors were encountered: