Sets node count for default pool equal to total desired node count to correctly size master #673
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
Closes #615
What is changed and how does it work?
GKE master node is sized initially to expect 5 or fewer nodes when first provisioned, or the size of the default node pool. Previously, the initial node count for the default pool was 1 (3 total because one per availability zone), so when the rest of the node pools get provisioned, GKE would then upgrade the master node to accommodate the rest of the nodes. This change sets the initial node count of the default pool to be equal to the sum of the node counts for the other pools (pd, tikv, tidb, monitor). With this, the master node is correctly sized and does not upgrade shortly after creating the cluster, as it did previously.
Check List
Tests
terraform apply
to GKECode changes
Does this PR introduce a user-facing change?: