From ea84a86009458cbcd9a9ae3d5da88221b4da8a9c Mon Sep 17 00:00:00 2001 From: Katie Horne Date: Wed, 13 Oct 2021 10:58:55 -0500 Subject: [PATCH] update AWS verbiage re: multi-zone clusters --- setup/kubernetes/aws.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/setup/kubernetes/aws.md b/setup/kubernetes/aws.md index c0997ab40..a3dacaa86 100644 --- a/setup/kubernetes/aws.md +++ b/setup/kubernetes/aws.md @@ -36,13 +36,11 @@ EC2 instance from AWS' > [container-based virtual machines (CVMs)](../../workspaces/cvms.md) unless > you're running Coder in a bare-metal Kubernetes environment. -### Single vs. multi-zone clusters +### Using multi-zone clusters -In our experience, single-region, single-zone clusters work best for Coder. - -However, if you opt for a multi-zone cluster, your workspace pods can only be -scheduled where you initially provisioned them. As such, make sure that there -are nodes available in each zone. Please note, however, that if a zone becomes +If you opt for a multi-zone cluster, your workspace pods can only be scheduled +where you initially provisioned them. As such, make sure that there are nodes +available in each zone. Please note, however, that if a zone becomes unavailable, the workspace pods will be unavailable because the persistent volumes are tied to the zone.