Skip to content

docs: additional kubernetes clusters #7019

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Apr 5, 2023
Merged

docs: additional kubernetes clusters #7019

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
033e844
docs: additional kubernetes clusters
bpmct Apr 5, 2023
4f35ff4
fmt and change wording
bpmct Apr 5, 2023
403f49c
fmt
bpmct Apr 5, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
fmt and change wording
  • Loading branch information
@bpmct
bpmct committed Apr 5, 2023
commit 4f35ff4b423bdb31dd3ca58e9bada1670e38a86a
4 changes: 1 addition & 3 deletions docs/manifest.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,5 @@
{
"versions": [
"main"
],
"versions": ["main"],
"routes": [
{
"title": "About",
Expand Down
33 changes: 16 additions & 17 deletions docs/platforms/kubernetes/additional-clusters.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,45 +9,47 @@ With Coder, you can deploy workspaces in additional Kubernetes clusters using di
First, create a kubeconfig file with [multiple contexts](https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/).

```sh
$ kubectl config get-contexts
$ kubectl config get-contexts

CURRENT NAME CLUSTER
workspaces-europe-west2-c workspaces-europe-west2-c
* workspaces-us-central1-a workspaces-us-central1-a
CURRENT NAME CLUSTER
workspaces-europe-west2-c workspaces-europe-west2-c
* workspaces-us-central1-a workspaces-us-central1-a
```

### Kubernetes control plane

If you deployed Coder on Kubernetes, you can attach a kubeconfig as a secret.
If you deployed Coder on Kubernetes, you can attach a kubeconfig as a secret.

This assumes Coder is deployed on the `coder` namespace and your kubeconfig file is in ~/.kube/config.

```sh
kubectl create secret generic kubeconfig-secret -n coder--from-file=~/.kube/config
```

Modify your helm values to mount the secret and [upgrade Coder](http://localhost:3000/docs/v2/latest/install/kubernetes#upgrading-coder-via-helm)
Modify your helm values to mount the secret:

```yaml
coder:
# ...
volumes:
- name: "kubeconfig-mount"
secret:
secretName: "kubeconfig-secret"
- name: "kubeconfig-mount"
secret:
secretName: "kubeconfig-secret"
volumeMounts:
- name: "kubeconfig-mount"
mountPath: "/mnt/secrets/kube"
readOnly: true
- name: "kubeconfig-mount"
mountPath: "/mnt/secrets/kube"
readOnly: true
```

[Upgrade Coder](http://localhost:3000/docs/v2/latest/install/kubernetes#upgrading-coder-via-helm) with these new values.

### VM control plane

If you deployed Coder on a VM, copy the kubeconfig file to `/home/coder/.kube/config`.

### Create a Coder template

You can start from our [example template](https://github.com/coder/coder/tree/main/examples/templates/kubernetes). From there, add [template parameters](../../templates/parameters.md) to allow developers to pick their desired cluster.
You can start from our [example template](https://github.com/coder/coder/tree/main/examples/templates/kubernetes). From there, add [template parameters](../../templates/parameters.md) to allow developers to pick their desired cluster.

```hcl
# main.tf
Expand Down Expand Up @@ -75,11 +77,9 @@ provider "kubernetes" {
}
```



## Option 2) Kubernetes ServiceAccounts

Alternatively, you can authenticate with remote clusters with ServiceAccount tokens. Coder can store these secrets on your behalf with [managed Terraform variables](../../templates/parameters.md#managed-terraform-variables).
Alternatively, you can authenticate with remote clusters with ServiceAccount tokens. Coder can store these secrets on your behalf with [managed Terraform variables](../../templates/parameters.md#managed-terraform-variables).

Alternatively, these could also be fetched from Kubernetes secrets or even [Hashicorp Vault](https://registry.terraform.io/providers/hashicorp/vault/latest/docs/data-sources/generic_secret).

Expand Down Expand Up @@ -185,7 +185,6 @@ $ export CLUSTER_ADDRESS=https://example.domain:6443

To fetch the CA certificate and token:


```sh
export CLUSTER_CA_CERTIFICATE=$(kubectl get secrets coder-service-account-token -n coder-workspaces -o jsonpath="{.data.ca\.crt}")

Expand Down