You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the configuration above - notice that it doesn't specify initial_node_count in the embedded node_pool - a new cluster with a node pool of size 1 is created.
Actual Behavior
A node pool with size 0 is created:
The cluster is not auto-resized above size 0 even if non kube-system pods are deployed:
Steps to Reproduce
terraform apply the config included above
Workaround
I can fix the issue by specifying initial_node_count = 1 explicitly.
But according to google_container_cluster docs initial_node_count is deprecated and node_count should be used instead. Unfortunately, I cannot use node_count with autoscaling configuration as node_count always sets the cluster size to node_count value when the actual size has been modified by autoscaler - thus usage of autoscaling and node_count is mutually exclusive.
I am concerned that support for initial_node_count will be dropped and it won't be possible to workaround the issue I have (cluster created with size 0) just by specifying initial_node_count.
The text was updated successfully, but these errors were encountered:
According to GKE API reference initialNodeCount is mandatory thus I think it shouldn't be deprecated in terraform-provider-google. It's value has to be within auto-scaling range.
If it's not present in tf configuration and auto-scaling is used then it could be defaulted to min_node_count.
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
locked and limited conversation to collaborators
Mar 29, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform Version
Terraform v0.11.3
Affected Resource
google_container_cluster
Terraform Configuration Files
Expected Behavior
With the configuration above - notice that it doesn't specify
initial_node_count
in the embeddednode_pool
- a new cluster with a node pool of size 1 is created.Actual Behavior
A node pool with size 0 is created:
The cluster is not auto-resized above size 0 even if non kube-system pods are deployed:
Steps to Reproduce
terraform apply
the config included aboveWorkaround
I can fix the issue by specifying
initial_node_count = 1
explicitly.But according to
google_container_cluster
docsinitial_node_count
is deprecated andnode_count
should be used instead. Unfortunately, I cannot usenode_count
with autoscaling configuration asnode_count
always sets the cluster size tonode_count
value when the actual size has been modified by autoscaler - thus usage of autoscaling andnode_count
is mutually exclusive.I am concerned that support for
initial_node_count
will be dropped and it won't be possible to workaround the issue I have (cluster created with size 0) just by specifyinginitial_node_count
.The text was updated successfully, but these errors were encountered: