Dalton Hubble 3fcb04f68c Improve apiserver backend service zone spanning ... * 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		2019-07-05 19:46:26 -07:00
..
container-linux/kubernetes	Improve apiserver backend service zone spanning	2019-07-05 19:46:26 -07:00
ignore	Remove Fedora Atomic modules	2019-06-23 13:40:51 -07:00