update AWS verbiage re: multi-zone clusters (coder#668)

Katie Horne · web-flow · commit de8f94101a5e · 2021-10-13T11:18:32.000-05:00
diff --git 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.
 
