Coder Enterprise Hub

Welcome to the Coder Enterprise hub. You'll find comprehensive guides and documentation to help you start working with Coder as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    Changelog

1a: Amazon Elastic Kubernetes Engine

If you already have a Kubernetes cluster running that meets Coder's requirements, you can skip these steps and proceed to Installation. Otherwise, follow this deployment guide set up an Amazon Elastic Kubernetes Engine cluster on which Coder can deploy.

Before proceeding, please make sure that you have the eksctl command line utility installed on your machine.

The following will spin up a Kubernetes cluster using the eksctl command; replace the parameters and environment variables as needed to reflect those for your environment.

    eksctl create cluster \
    --name "$CLUSTER_NAME" \
    --version 1.17 \
    --region "$REGION" \
    --nodegroup-name standard-workers \
    --node-type t3.medium \
    --nodes 2 \
    --nodes-min 2 \
    --nodes-max 8 \
    --ssh-access \
    --ssh-public-key "$SSH_KEY_PATH" \

Once the cluster is created, you'll need to adjust the Kubernetes storage class that is created by default to support immediate volume binding.

First, delete the gp2 storage class:

kubectl delete sc gp2

Next, recreate the gp2 storage class with the volumeBindingMode set to Immediate:

cat <<EOF | kubectl apply -f -
kind: StorageClass
  annotations: "true"
  name: gp2
  type: gp2
  fsType: ext4
volumeBindingMode: Immediate


We recommend running Coder in a separate namespace; to do so:

  1. Create your namespace:

    kubectl create namespace coder
  2. Change the kubectl context to point to your newly created namespace:

    kubectl config set-context --current --namespace=coder

At this point, you are set up and ready to install Coder onto your cluster.

Updated about a month ago

1a: Amazon Elastic Kubernetes Engine

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.