From 61cc7e9be958a3cc4ee5903c59f8b87ff07b4b92 Mon Sep 17 00:00:00 2001 From: Steve McMaster Date: Fri, 4 Nov 2022 16:51:34 -0400 Subject: [PATCH] test --- .drone.yml | 24 +++++++++ kubernetes/README.md | 113 ++++++++++++++++++++++++++++++++++++++++++ kubernetes/main.tf | 114 +++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 251 insertions(+) create mode 100644 .drone.yml create mode 100644 kubernetes/README.md create mode 100644 kubernetes/main.tf diff --git a/.drone.yml b/.drone.yml new file mode 100644 index 0000000..2a26acf --- /dev/null +++ b/.drone.yml @@ -0,0 +1,24 @@ +kind: pipeline +name: default +type: docker + +steps: + - name: install coder cli + image: alpine:3.16 + commands: + - curl -L https://coder.com/install.sh | sh + - name: push templates + image: ghcr.io/coder/coder:v0.11.0 + environment: + CODER_URL: http://coder.coder.svc.cluster.local + CODER_SESSION_TOKEN: + from_secret: CODER_SESSION_TOKEN + CODER_TEMPLATE_VERSION: $${DRONE_COMMIT_SHA} + commands: + - apk add git + - | + for template in * ; do + [ -e "$template/main.tf" ] || continue + coder templates push -d $template --yes $template || \ + coder templates create -d $template --yes $template + done diff --git a/kubernetes/README.md b/kubernetes/README.md new file mode 100644 index 0000000..6e8bbf6 --- /dev/null +++ b/kubernetes/README.md @@ -0,0 +1,113 @@ +--- +name: Develop in Kubernetes +description: Get started with Kubernetes development. +tags: [cloud, kubernetes] +--- + +# Getting started + +This template creates a pod running the `codercom/enterprise-base:ubuntu` image. + +## RBAC + +The Coder provisioner requires permission to administer pods to use this template. The template +creates workspaces in a single Kubernetes namespace, using the `workspaces_namespace` parameter set +while creating the template. + +Create a role as follows and bind it to the user or service account that runs the coder host. + +```yaml +apiVersion: rbac.authorization.k8s.io/v1 +kind: Role +metadata: + name: coder +rules: + - apiGroups: [""] + resources: ["pods"] + verbs: ["*"] +``` + +## Authentication + +This template can authenticate using in-cluster authentication, or using a kubeconfig local to the +Coder host. For additional authentication options, consult the [Kubernetes provider +documentation](https://registry.terraform.io/providers/hashicorp/kubernetes/latest/docs). + +### kubeconfig on Coder host + +If the Coder host has a local `~/.kube/config`, you can use this to authenticate +with Coder. Make sure this is done with same user that's running the `coder` service. + +To use this authentication, set the parameter `use_kubeconfig` to true. + +### In-cluster authentication + +If the Coder host runs in a Pod on the same Kubernetes cluster as you are creating workspaces in, +you can use in-cluster authentication. + +To use this authentication, set the parameter `use_kubeconfig` to false. + +The Terraform provisioner will automatically use the service account associated with the pod to +authenticate to Kubernetes. Be sure to bind a [role with appropriate permission](#rbac) to the +service account. For example, assuming the Coder host runs in the same namespace as you intend +to create workspaces: + +```yaml +apiVersion: v1 +kind: ServiceAccount +metadata: + name: coder + +--- +apiVersion: rbac.authorization.k8s.io/v1 +kind: RoleBinding +metadata: + name: coder +subjects: + - kind: ServiceAccount + name: coder +roleRef: + kind: Role + name: coder + apiGroup: rbac.authorization.k8s.io +``` + +Then start the Coder host with `serviceAccountName: coder` in the pod spec. + +## Namespace + +The target namespace in which the pod will be deployed is defined via the `coder_workspace` +variable. The namespace must exist prior to creating workspaces. + +## Persistence + +The `/home/coder` directory in this example is persisted via the attached PersistentVolumeClaim. +Any data saved outside of this directory will be wiped when the workspace stops. + +Since most binary installations and environment configurations live outside of +the `/home` directory, we suggest including these in the `startup_script` argument +of the `coder_agent` resource block, which will run each time the workspace starts up. + +For example, when installing the `aws` CLI, the install script will place the +`aws` binary in `/usr/local/bin/aws`. To ensure the `aws` CLI is persisted across +workspace starts/stops, include the following code in the `coder_agent` resource +block of your workspace template: + +```terraform +resource "coder_agent" "main" { + startup_script = <