You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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):
0 commit comments