Skip to content

Commit 221b431

Browse files
author
gentele
committed
add docs for RBAC requirements
1 parent 7356c04 commit 221b431

1 file changed

Lines changed: 60 additions & 0 deletions

File tree

docs/docs/advanced/rbac.md

Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
---
2+
title: RBAC / Permissions
3+
---
4+
5+
To start Tiller within your cluster, you need to ensure that your Kubernetes user must be admin in all namespaces that you are using and that your user has the permission to create ClusterRoles and ClusterRoleBindings in the namespace for the tiller release.
6+
7+
If you run into permission errors, please create the following resources in your cluster:
8+
9+
Role:
10+
```yaml
11+
apiVersion: rbac.authorization.k8s.io/v1
12+
kind: Role
13+
metadata:
14+
name: devspace-user
15+
rules:
16+
- apiGroups:
17+
- ""
18+
resources:
19+
- serviceaccounts
20+
verbs:
21+
- create
22+
- delete
23+
- deletecollection
24+
- get
25+
- list
26+
- patch
27+
- update
28+
- watch
29+
- apiGroups:
30+
- rbac.authorization.k8s.io
31+
resources:
32+
- rolebindings
33+
- roles
34+
verbs:
35+
- create
36+
- delete
37+
- deletecollection
38+
- get
39+
- list
40+
- patch
41+
- update
42+
- watch
43+
```
44+
45+
RoleBinding (make sure to replace $USERNAME within the last line):
46+
```yaml
47+
apiVersion: rbac.authorization.k8s.io/v1
48+
kind: RoleBinding
49+
metadata:
50+
name: devspace-user-binding
51+
namespace: default
52+
roleRef:
53+
apiGroup: rbac.authorization.k8s.io
54+
kind: Role
55+
name: devspace-user
56+
subjects:
57+
- apiGroup: rbac.authorization.k8s.io
58+
kind: User
59+
name: $USERNAME
60+
```

0 commit comments

Comments
 (0)