Skip to content

update AWS verbiage re: multi-zone clusters #668

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 13, 2021
Merged

update AWS verbiage re: multi-zone clusters #668

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 4 additions & 6 deletions setup/kubernetes/aws.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down