-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Autoscaling cannot be disabled #83
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
Comments
Autoscaling is our best practice by default - do you have a use case where specifying max_node_count isn't sufficient? |
Hi @morgante! That's my current workaround, yes -- but one use case where it's insufficient is where we want to freeze the current nodepool at zero without additional commands, and prevent it from spinning up new nodes, since |
Got it - unfortunately it's tough to have a conditional block in Terraform. If this is a major issue, could you file a provider bug requesting a disabled/enabled flag on the autoscaling block? If there is one, we'd be happy to add it to the module. |
Hi @nixsticks. Would you like to proceed with an issue on the Google provider or can we close this issue? |
Hey @aaron-lane , sorry I didn't follow up on this! We've managed to work around it for now, so no need to file a provider bug / add to the module, I think. |
FYI we are now going to look at doing this with Terraform 0.12. See #249. |
It appears that users must either specify
min_node_count
andmax_node_count
or have them default to 1 and 100; theautoscaling
block is always created. Is this by design, or might we in future be able to specify a static node count and disable autoscaling?The text was updated successfully, but these errors were encountered: