Skip to content

Commit 45776e5

Browse files
authored
docs: remove RBAC section (#7040)
1 parent fb44dc6 commit 45776e5

File tree

2 files changed

+8
-38
lines changed

2 files changed

+8
-38
lines changed

examples/templates/kubernetes-with-podman/README.md

Lines changed: 4 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -13,25 +13,6 @@ This template creates [rootless podman](./images) pods with either an Ubuntu or
1313
1414
Base images are pushed to [Docker Hub](https://hub.docker.com//codercom)
1515

16-
## RBAC
17-
18-
The Coder provisioner requires permission to administer pods to use this template. The template
19-
creates workspaces in a single Kubernetes namespace, using the `workspaces_namespace` parameter set
20-
while creating the template.
21-
22-
Create a role as follows and bind it to the user or service account that runs the coder host.
23-
24-
```yaml
25-
apiVersion: rbac.authorization.k8s.io/v1
26-
kind: Role
27-
metadata:
28-
name: coder
29-
rules:
30-
- apiGroups: [""]
31-
resources: ["pods"]
32-
verbs: ["*"]
33-
```
34-
3516
## Authentication
3617

3718
This template can authenticate using in-cluster authentication, or using a kubeconfig local to the
@@ -79,6 +60,10 @@ roleRef:
7960
8061
Then start the Coder host with `serviceAccountName: coder` in the pod spec.
8162

63+
### Authenticate against external clusters
64+
65+
You may want to deploy workspaces on a cluster outside of the Coder control plane. Refer to the [Coder docs](https://coder.com/docs/v2/latest/platforms/kubernetes/additional-clusters) to learn how to modify your template to authenticate against external clusters.
66+
8267
## Namespace
8368

8469
The target namespace in which the pod will be deployed is defined via the `coder_workspace`

examples/templates/kubernetes/README.md

Lines changed: 4 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -9,25 +9,6 @@ icon: /icon/k8s.png
99

1010
This template creates a pod running the `codercom/enterprise-base:ubuntu` image.
1111

12-
## RBAC
13-
14-
The Coder provisioner requires permission to administer pods to use this template. The template
15-
creates workspaces in a single Kubernetes namespace, using the `workspaces_namespace` parameter set
16-
while creating the template.
17-
18-
Create a role as follows and bind it to the user or service account that runs the coder host.
19-
20-
```yaml
21-
apiVersion: rbac.authorization.k8s.io/v1
22-
kind: Role
23-
metadata:
24-
name: coder
25-
rules:
26-
- apiGroups: [""]
27-
resources: ["pods"]
28-
verbs: ["*"]
29-
```
30-
3112
## Authentication
3213

3314
This template can authenticate using in-cluster authentication, or using a kubeconfig local to the
@@ -75,6 +56,10 @@ roleRef:
7556
7657
Then start the Coder host with `serviceAccountName: coder` in the pod spec.
7758

59+
### Authenticate against external clusters
60+
61+
You may want to deploy workspaces on a cluster outside of the Coder control plane. Refer to the [Coder docs](https://coder.com/docs/v2/latest/platforms/kubernetes/additional-clusters) to learn how to modify your template to authenticate against external clusters.
62+
7863
## Namespace
7964

8065
The target namespace in which the pod will be deployed is defined via the `coder_workspace`

0 commit comments

Comments
 (0)