chore: refactor CVMs docs

Author: Katie Horne

admin/workspace-management/cvms.md

@@ -0,0 +1,63 @@
+---
+title: Cluster setup
+description: Learn how to set up K8s clusters capable of supporting CVMs.
+---
+
+The following sections show how you can set up your Kubernetes clusters hosted
+by Google, Azure, and Amazon to support CVMs.
+
+## Google Cloud Platform w/ GKE
+
+To use CVMs with GKE, [create a cluster](../../setup/kubernetes/google.md) using
+the following parameters:
+
+- GKE Master version `latest`
+- `node-version = "latest"`
+- `image-type = "UBUNTU"`
+
+For example:
+
+```console
+gcloud beta container clusters create "YOUR_NEW_CLUSTER" \
+    --node-version "latest" \
+    --cluster-version "latest" \
+    --image-type "UBUNTU"
+    ...
+```
+
+## Azure Kubernetes Service
+
+If you're using Kubernetes version 1.18, Azure defaults to the correct Ubuntu
+node base image. When
+[creating your cluster](../../../setup/Kubernetes/azure.md), set
+`--kubernetes-version` to `1.18.x` or newer for CVMs.
+
+## Amazon Web Services w/ EKS
+
+You can modify an existing [AWS-hosted container](../../setup/kubernetes/aws.md)
+to support CVMs by
+[creating a nodegroup](https://eksctl.io/usage/managing-nodegroups/#creating-a-nodegroup-from-a-config-file)
+and updating your `eksctl` config spec.
+
+1. Define your config file in the location of your choice (we've named the file
+   `coder-node.yaml`, but you can call it whatever you'd like):
+
+   ```yaml
+   apiVersion: eksctl.io/v1alpha5
+   kind: ClusterConfig
+
+   metadata:
+     version: "1.17"
+     name: <YOUR_CLUSTER_NAME>
+     region: <YOUR_AWS_REGION>
+
+   nodeGroups:
+     - name: coder-node-group
+       amiFamily: Ubuntu1804
+   ```
+
+1. Create your nodegroup (be sure to provide the correct file name):
+
+   ```console
+   eksctl create nodegroup --config-file=coder-node.yaml
+   ```

admin/workspace-management/cvms/cluster-setup.md

@@ -0,0 +1,70 @@
+---
+title: Images
+description: Learn how to work with images for CVM-enabled workspaces.
+---
+
+This article walks you through how to configure images for use with CVMs, as
+well as how to access images located in private registries.
+
+## Image configuration
+
+The following sections show how you can configure your image to include systemd
+and Docker for use in CVMs.
+
+### systemd
+
+If your image's OS distribution doesn't link the `systemd` init to `/sbin/init`,
+you'll need to do this manually in your Dockerfile.
+
+The following snippet shows how you can specify `systemd` as the init in your
+image:
+
+```Dockerfile
+FROM ubuntu:20.04
+RUN apt-get update && apt-get install -y \
+    build-essential \
+    systemd
+
+# use systemd as the init
+RUN ln -s /lib/systemd/systemd /sbin/init
+```
+
+When you start up a workspace, Coder checks for the presence of `/sbin/init` in
+your image. If it exists, then Coder uses it as the container entrypoint with a
+`PID` of 1.
+
+### Docker
+
+To add Docker, install the `docker` packages into your image. For a seamless
+experience, use [systemd](#systemd) and register the `docker` service so
+`dockerd` runs automatically during initialization.
+
+The following snippet shows how your image can register the `docker` services in
+its Dockerfile.
+
+```Dockerfile
+FROM ubuntu:20.04
+RUN apt-get update && apt-get install -y \
+    build-essential \
+    git \
+    bash \
+    docker.io \
+    curl \
+    sudo \
+    systemd
+
+# Enables Docker starting with systemd
+RUN systemctl enable docker
+
+# use systemd as the init
+RUN ln -s /lib/systemd/systemd /sbin/init
+```
+
+## Private registries
+
+To use CVM workspaces with private images, you **must** create a
+[registry](../registries/index.md#adding-a-registry) with authentication
+credentials. Private images that can be pulled directly by the node will not
+work with CVMs.
+
+This restriction is removed if you enable [cached CVMs](#enabling-cached-cvms).