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
RITESHBRID opened this issue
Jan 28, 2022
· 3 comments
Labels
breakingP4low priority issuesrefactorUpdates for readability, code cleanliness, DRYness, etc. Only needs Terraform exp.triagedScoped and ready for work
initial_node_count is only used for the default pool (that we delete anyways) and is therefore intentionally ignored.
We should probably remove it from the module entirely, but that will require additional refactoring.
If you want to change the number of nodes in your cluster, you should adjust the size of your node pools. There is actually no reason to adjust the number at any time.
morgante
added
breaking
P4
low priority issues
refactor
Updates for readability, code cleanliness, DRYness, etc. Only needs Terraform exp.
triaged
Scoped and ready for work
and removed
bug
Something isn't working
labels
Jan 31, 2022
@morgante I my case, I have down scaled my gke cluster to size 0 through GCP console, Now I have tried to upscale the cluster through terraform, I have changed min_count to 5 but still cluster is not spine up new nodes to match min node count. However GCP console show the Min count has been updated in autoscale
breakingP4low priority issuesrefactorUpdates for readability, code cleanliness, DRYness, etc. Only needs Terraform exp.triagedScoped and ready for work
TL;DR
Whenever we try to update initial_node_count variable, terrafrom plan and apply did not show any changes
Expected behavior
initial_node_count must be updated through terraform
Observed behavior
No response
Terraform Configuration
Terraform Version
Additional information
No response
The text was updated successfully, but these errors were encountered: