* docs: add kubestream docs and update example template * make fmt * add to template's README * add the seperate page * make fmt * make fmt * add namespace to deployment resource * fmt * add screenshots * link docs in template * Add remaining examples * enable deployments requirement * Update deployment-logs.md * rewording * fix spelling * how? * cleanup * Update docs/platforms/kubernetes/deployment-logs.md Co-authored-by: Ben Potter <ben@coder.com> * suggestions * use online link * refine --------- Co-authored-by: Eric <ericpaulsen@coder.com> Co-authored-by: Ben Potter <ben@coder.com>
name, description, tags, icon
name | description | tags | icon | ||
---|---|---|---|---|---|
Develop in Kubernetes | Get started with Kubernetes development. |
|
/icon/k8s.png |
Getting started
This template creates a deplyment running the codercom/enterprise-base:ubuntu
image.
Prerequisites
This template uses kubernetes_deployment
terraform resource, which requires the coder
service account to have permission to create deploymnets. For example if you are using helm to install Coder, you should set coder.serviceAccount.enableDeployments=true
in your values.yaml
coder:
serviceAccount:
workspacePerms: true
- enableDeployments: false
+ enableDeployments: true
annotations: {}
name: coder
Note: This is only required for Coder versions < 0.28.0, as this will be the default value for Coder versions >= 0.28.0
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.
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 to the service account. For example, assuming the Coder host runs in the same namespace as you intend to create workspaces:
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.
Authenticate against external clusters
You may want to deploy workspaces on a cluster outside of the Coder control plane. Refer to the Coder docs to learn how to modify your template to authenticate against external clusters.
Namespace
The target namespace in which the deployment 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:
resource "coder_agent" "main" {
startup_script = <<-EOT
set -e
# install AWS CLI
curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
unzip awscliv2.zip
sudo ./aws/install
EOT
}
code-server
code-server
is installed via the startup_script
argument in the coder_agent
resource block. The coder_app
resource is defined to access code-server
through
the dashboard UI over localhost:13337
.
Deployment logs
To stream kubernetes pods events from the deployment, you can use Coder's coder-logstream-kube
tool. This can stream logs from the deployment to Coder's workspace startup logs. You just need to install the coder-logstream-kube
helm chart on the cluster where the deployment is running.
helm repo add coder-logstream-kube https://helm.coder.com/logstream-kube
helm install coder-logstream-kube coder-logstream-kube/coder-logstream-kube \
--namespace coder \
--set url=<your-coder-url-including-http-or-https>
For detailed instructions, see Deployment logs