diff --git a/setup/kubernetes/aws.md b/setup/kubernetes/aws.md index a3dacaa86..06b39b327 100644 --- a/setup/kubernetes/aws.md +++ b/setup/kubernetes/aws.md @@ -36,14 +36,6 @@ EC2 instance from AWS' > [container-based virtual machines (CVMs)](../../workspaces/cvms.md) unless > you're running Coder in a bare-metal Kubernetes environment. -### Using multi-zone clusters - -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. - ## Preliminary steps Before you can create a cluster, you'll need to perform the following to set up @@ -188,8 +180,11 @@ as a workspace deployment option, you'll need to nodeGroups: - name: coder-node-group amiFamily: Ubuntu2004 + ami: ``` +> [See here for a list of Ubuntu AMIs](https://cloud-images.ubuntu.com/locator/ec2/) + 1. Create your nodegroup (be sure to provide the correct file name): ```console diff --git a/setup/requirements.md b/setup/requirements.md index 4cf2d5b68..f792e8f04 100644 --- a/setup/requirements.md +++ b/setup/requirements.md @@ -81,7 +81,7 @@ Additionally, you must enable [dynamic volume provisioning](https://kubernetes.io/docs/concepts/storage/dynamic-provisioning/#enabling-dynamic-provisioning) so that Coder can mount the PVC to the workspace (if you're using a custom `StorageClass`, be sure that it supports DVP. Otherwise, Coder cannot provision -workspaces. +workspaces). ## Database