Feature: Uniformly distribute nodes across zones by default #1629
Labels
feature
New feature
good first issue
Good for newcomers
groomed
Task that everybody agrees to pass the gatekeeper
Motivation
Typically a cloud provider region consists of several zones, which represent isolated datacenters in geographical proximity, or in some cases isolated "fire-cells" in the same datacenter.
There's a general recommendation, to spread the cluster-nodes in the same region across these availability zones for resiliency reasons. Claudie doesn't respect this well enough.
As an example - creating a new nodepool currently requires a region + zone specification. Imagine a cluster with a single nodepool, that's autoscaled - all the nodes will be created in the same availability zone. And if that zone is under an outage, the whole cluster workload is having an outage as well.
If the workload was spread out, let's say across 3 zones, only 1/3 of the workload services would have an outage should a single zone die.
Description
Make the following specs optional on AWS/Azure/GCP/OCI/Hetzner:
nodePools.dynamic[].providerSpec.zone
.If the
providerSpec.zone
is not specified, then theterraformer
templates are enhanced to:node id % zone-count
approach) to each new nodeproviderSpec.zone
is still respected, if specifiedExit criteria
providerSpec.zone
is optional1
The text was updated successfully, but these errors were encountered: