-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Fix issue with regional cluster roll outs causing version skews #108
Fix issue with regional cluster roll outs causing version skews #108
Conversation
39b30d8
to
809d43d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a number of unrelated changes in this PR that I'd like to get trimmed down, if possible we should handle stale doc fixups in a separate PR.
1b5cad5
to
7aa4893
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few issues to clear up. Additionally, the integration test for autoupgrade is failing.
a49278d
to
9c5dab5
Compare
Regional clusters are created using the newest version of GKE that is available across all zones in which the masters live. When a GKE version roll out occurs, the available versions across the zones can become skewed for zonal clusters with version x.y.z-gke.a being the only available zonal version in one zone but version x.y[+1].z[+1]-gke.a[+1] being the only zonal version available in another zone. The Terraform module only checks for the version available in the first zone returned by a call to the google_compute_zones data resource. Consequently, the module will fail to create a regional cluster during a roll out due to the version available in that zone not being available across all the zones for regional clusters.
9c5dab5
to
1d73e9d
Compare
@@ -24,6 +24,11 @@ provider "google" { | |||
version = "~> 1.20" | |||
} | |||
|
|||
provider "google-beta" { | |||
credentials = "${file(var.credentials_path)}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it appropriate to pin the provider version here?
@@ -24,6 +24,11 @@ provider "google" { | |||
region = "${var.region}" | |||
} | |||
|
|||
provider "google-beta" { | |||
credentials = "${file(var.credentials_path)}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it appropriate to pin the provider version here?
@@ -23,6 +23,11 @@ provider "google" { | |||
region = "${var.region}" | |||
} | |||
|
|||
provider "google-beta" { | |||
credentials = "${file(var.credentials_path)}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it appropriate to pin the provider version here?
@@ -24,6 +24,11 @@ provider "google" { | |||
region = "${var.region}" | |||
} | |||
|
|||
provider "google-beta" { | |||
credentials = "${file(var.credentials_path)}" | |||
region = "${var.region}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it appropriate to pin the provider version here?
…/ds/fix-version-skews Fix issue with regional cluster roll outs causing version skews
Regional clusters are created using the newest version of GKE that is
available across all zones in which the masters live. When a GKE version
roll out occurs, the available versions across the zones can become
skewed for zonal clusters with version x.y.z-gke.a being the only
available zonal version in one zone but version x.y[+1].z[+1]-gke.a[+1]
being the only zonal version available in another zone.
The Terraform module only checks for the version available in the first
zone returned by a call to the google_compute_zones data resource.
Consequently, the module will fail to create a regional cluster during a
roll out due to the version available in that zone not being available
across all the zones for regional clusters.