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

1b: Azure Kubernetes Service

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 to set up an Azure Kubernetes Service (AKS) cluster on which Coder can deploy.

Before proceeding, please make sure that you have the Azure CLI installed on your machine.

Step 1: Create the Resource Group

Create a resource group using the following command (be sure to set the $RESOURCE_GROUP and $LOCATION environment variables accordingly):

az group create \
    --resource-group "$RESOURCE_GROUP" \
    --location "$LOCATION"

Step 2: Create the Azure Kubernetes Service Cluster

Run the following to create the Azure Kubernetes Service Cluster (be sure to replace the placeholder and environment variables with the values that are applicable to you):

# You may have to run `az extension add --name aks-preview`
# You may also need to create a service principal manually using
# `az ad sp create-for-rbac --skip-assignment`, then setting the
# --service-principal and --client-secret flags

az aks create \
    --name "$CLUSTER_NAME" \
    --resource-group "$RESOURCE_GROUP" \
    --subscription "$SUBSCRIPTION" \
    --generate-ssh-keys \
    --enable-addons http_application_routing \
    --enable-cluster-autoscaler \
    --location "$LOCATION" \
    --max-count 10 \
    --min-count 2 \
    --node-vm-size Standard_B8ms \
    --network-plugin "kubenet" \
    --network-policy "calico"

Step 3: Post-Deployment

After deploying your AKS cluster, you will need to configure kubectl to point to your cluster. To do so:

  1. If you haven't already, install the Azure CLI and kubectl
  2. Initialize kubectl with the cluster credentials:
az aks get-credentials --name "$CLUSTER_NAME" --resource-group "$RESOURCE_GROUP"
  1. We recommend running Coder in a separate namespace; to do so, run:
kubectl create namespace coder
  1. If you will be running Coder in a separate namespace, change the kubectl context to point to the 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

1b: Azure Kubernetes Service

Suggested Edits are limited on API Reference Pages

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