Skip to content

Commit ada4e9b

Browse files
author
Katie Horne
authored
chore: add usage notes re: single- and multi-zone EKS clusters (coder#645)
1 parent 2ec350e commit ada4e9b

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

setup/kubernetes/aws.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,16 @@ EC2 instance from AWS'
3636
> [container-based virtual machines (CVMs)](../../workspaces/cvms.md) unless
3737
> you're running Coder in a bare-metal Kubernetes environment.
3838
39+
### Single vs. multi-zone clusters
40+
41+
In our experience, single-region, single-zone clusters work best for Coder.
42+
43+
However, if you opt for a multi-zone cluster, your workspace pods can only be
44+
scheduled where you initially provisioned them. As such, make sure that there
45+
are nodes available in each zone. Please note, however, that if a zone becomes
46+
unavailable, the workspace pods will be unavailable because the persistent
47+
volumes are tied to the zone.
48+
3949
## Preliminary steps
4050

4151
Before you can create a cluster, you'll need to perform the following to set up

0 commit comments

Comments
 (0)