Skip to content

Commit f5d7a62

Browse files
authored
Merge pull request #780 from oracle/rmarano2
edit permissions command
2 parents 18fe0a4 + cc50bcf commit f5d7a62

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

site/helm-charts.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -17,23 +17,23 @@ The WebLogic Kubernetes Operator uses Helm to create and deploy any necessary re
1717
Helm has two parts: a client (Helm) and a server (Tiller). Tiller runs inside of your Kubernetes cluster, and manages releases (installations) of your charts. See https://github.com/kubernetes/helm/blob/master/docs/install.md for detailed instructions on installing Helm and Tiller.
1818

1919
In order to use Helm to install and manage the operator, you need to ensure that the service account that Tiller uses
20-
has the `cluster-admin` role. The default would be `default` in namespace `kube-system`. You can give that Service
21-
Account the necessary permissions with this command:
20+
has the `cluster-admin` role. The default would be `default` in namespace `kube-system`. You can give that service
21+
account the necessary permissions with this command:
2222

2323
```
2424
cat << EOF | kubectl apply -f -
25-
apiVersion: rbac.authorization.k8s.io/v1beta1
25+
apiVersion: rbac.authorization.k8s.io/v1
2626
kind: ClusterRoleBinding
2727
metadata:
28-
name: tiller-cluster-admin
28+
name: helm-user-cluster-admin-role
2929
roleRef:
30+
apiGroup: rbac.authorization.k8s.io
31+
kind: ClusterRole
3032
name: cluster-admin
3133
subjects:
3234
- kind: ServiceAccount
3335
name: default
3436
namespace: kube-system
35-
userNames:
36-
- system:serviceaccount:kube-system:default
3737
EOF
3838
```
3939

0 commit comments

Comments
 (0)