Skip to content
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

Improve apiserver backend service zone spanning on GCP #504

Merged
merged 1 commit into from
Jul 6, 2019

Conversation

dghubble
Copy link
Member

@dghubble dghubble commented Jul 6, 2019

  • google_compute_backend_services use nested blocks to define backends (instance groups heterogeneous controllers)
  • Use Terraform v0.12.x dynamic blocks so the apiserver backend service can refer to (up to zone-many) controller instance groups
  • Previously, with Terraform v0.11.x, the apiserver backend service had to list a fixed set of backends to span controller nodes across zones in multi-controller setups. 3 backends were used because each
    GCP region offered at least 3 zones. Single-controller clusters had the cosmetic ugliness of unused instance groups
  • Allow controllers to span more than 3 zones in a region, if the region offers more than 3 zones (e.g. us-central1)

Related:

@dghubble dghubble changed the title Improve apiserver backend service zone spanning Improve apiserver backend service zone spanning on GCP Jul 6, 2019
* google_compute_backend_services use nested blocks to define
backends (instance groups heterogeneous controllers)
* Use Terraform v0.12.x dynamic blocks so the apiserver backend
service can refer to (up to zone-many) controller instance groups
* Previously, with Terraform v0.11.x, the apiserver backend service
had to list a fixed set of backends to span controller nodes across
zones in multi-controller setups. 3 backends were used because each
GCP region offered at least 3 zones. Single-controller clusters had
the cosmetic ugliness of unused instance groups
* Allow controllers to span more than 3 zones if avilable in a
region (e.g. currently only us-central1, with 4 zones)

Related:

* https://www.terraform.io/docs/providers/google/r/compute_backend_service.html
* https://www.terraform.io/docs/configuration/expressions.html#dynamic-blocks
@dghubble dghubble force-pushed the improve-gcp-zone-spanning branch from bd0116f to 3fcb04f Compare July 6, 2019 02:46
@dghubble dghubble merged commit 3fcb04f into master Jul 6, 2019
@dghubble dghubble deleted the improve-gcp-zone-spanning branch July 6, 2019 20:18
dghubble added a commit that referenced this pull request Jul 20, 2019
* Intended as part of #504 improvement
* Single controller clusters only require one controller
instance group (previously created zone-many)
* Multi-controller clusters must "wrap" controllers over
zonal heterogeneous instance groups. For example, 5
controllers over 3 zones (no change)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant