Coder on Azure Kubernetes (K8s) Service

This repo intends to mimic an enterprise-grade Coder deployment with configurations you'd expect from a Fortune 500 customer. These typically include:

• Multi-cloud, multi-platform workspace provisioning (see my webinar on this topic here)
• CI/CD automation for template lifecycle and K8s deployment
• Microsoft Entra ID Single Sign-On
• Managed PostgreSQL
• TLS certificates

Helm

/helm contains the values.yaml file used to configure the Coder K8s deployment and application. In-line comments provide context on the various sections and environment variables. A few things to note:

• Primary endpoint is eric-aks.demo.coder.com, pointing to an Azure Load Balancer
• Coder image is ericpaulsen/coder-{latest-version}:multi-cloud, which includes az & gcloud CLIs
• GCP, GKE service account key and kubeconfig is mounted into the Coder pod
• GitHub, GitLab, and JFrog Artifactory integrations enable access from Coder workspaces
• Terraform authenticates to Azure via a managed identity set in coder.podLabels
• Application state is stored in Azure Postgres Single Server

/cert-manager stores YAML configuration for the cert-manager, responsible for issuing, rotating TLS certificates for Coder. The certificate is created as a K8s TLS secret, and mounted into Coder using the coder.tls.secretNames value.

For more information on cert-manager, see here.

Templates

Templates are a Coder construct represented as Terraform files, used to provision infrastructure for the cloud development environment (Coder workspace). Each template in /templates corresponds to a unique development workflow or use-case, spelled out in the README.md file.

CI/CD Automation

Templates are pushed into Coder on each commit via GitHub Actions configured in .github/workflows/. The basic premise for this workflow is to push the template changes into Coder via the below commands:

coder login https://eric-aks.demo.coder.com
coder templates push <template-name>