You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The fix implemented in #19 does not work as expected in us-central1 due to this region having four zones.
Expected behavior
When creating a regional cluster with no zones explicitly defined, all zones within a region should be used.
Observed behavior
In us-central1, because of this region having four zones, the random_shuffle selects three out of four zones. If this list of three out of the four zones changes for any reason, terraform attemps to update the cluster and generates an error: Error: googleapi: Error 400: Cluster location change not allowed.
TL;DR
The fix implemented in #19 does not work as expected in us-central1 due to this region having four zones.
Expected behavior
When creating a regional cluster with no zones explicitly defined, all zones within a region should be used.
Observed behavior
In us-central1, because of this region having four zones, the random_shuffle selects three out of four zones. If this list of three out of the four zones changes for any reason, terraform attemps to update the cluster and generates an error: Error: googleapi: Error 400: Cluster location change not allowed.
Terraform Configuration
Terraform Version
Additional information
I suggest changing the random_shuffle to set result_count to length(data.google_compute_zones.available[0].names) rather than a static value.
The text was updated successfully, but these errors were encountered: