Change worker managed instance group to span zones in region

* Change Google Cloud module to require the `region` variable
* Workers are created in random zones within the given region
* Tolerate Google Cloud zone failures or capacity issues
* If workers are preempted (if enabled), replacement instances can
be drawn from any zone in the region, which should avoid scheduling
issues that were possible before if a single zone aggressively
preempts instances (presumably due to Google Cloud capacity)
This commit is contained in:
Dalton Hubble
2017-11-04 10:57:12 -07:00
parent e32885c9cd
commit 6300383b43
8 changed files with 26 additions and 11 deletions

View File

@ -3,9 +3,14 @@ variable "cluster_name" {
description = "Cluster name"
}
variable "region" {
type = "string"
description = "Google Cloud Region (e.g. us-central1, see `gcloud compute regions list`)"
}
variable "zone" {
type = "string"
description = "Google Cloud zone (e.g. us-central1-f, see `gcloud compute zones list`)"
description = "Google Cloud Zone (e.g. us-central1-f, see `gcloud compute zones list`)"
}
variable "dns_zone" {