opensource/coder
3
0
Fork 0
mirror of https://github.com/coder/coder.git synced 2026-09-24 15:04:27 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: remove RBAC section (#7040)

Browse Source
This commit is contained in:
Ben Potter
2023-04-10 21:57:00 -05:00
committed by GitHub
parent fb44dc653e
commit 45776e57f6
2 changed files with 8 additions and 38 deletions
Download Patch File Download Diff File Expand all files Collapse all files
examples/templates/kubernetes-with-podman/README.md
+4 -19
View File
@@ -13,25 +13,6 @@ This template creates [rootless podman](./images) pods with either an Ubuntu or
Base images are pushed to [Docker Hub](https://hub.docker.com//codercom)
## 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
@@ -79,6 +60,10 @@ roleRef:
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](https://coder.com/docs/v2/latest/platforms/kubernetes/additional-clusters) to learn how to modify your template to authenticate against external clusters.
## Namespace
The target namespace in which the pod will be deployed is defined via the `coder_workspace`
examples/templates/kubernetes/README.md
+4 -19
View File
@@ -9,25 +9,6 @@ icon: /icon/k8s.png
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
@@ -75,6 +56,10 @@ roleRef:
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](https://coder.com/docs/v2/latest/platforms/kubernetes/additional-clusters) to learn how to modify your template to authenticate against external clusters.
## Namespace
The target namespace in which the pod will be deployed is defined via the `coder_workspace`