-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
https://devopstales.github.io/kubernetes/k8s-helm-rbac/ #17
Comments
instead of service account can we give access to specific ad group , i have give role and role binding to one name space for AD group , but when the user is tried to install the application to the specific name it not allowing , how we can fix this issue? |
Hi @roshithrajan I want to clarify some tings first. This post is based on helm2. That is outdated now, we use helm3. As you can see in the post at helm2 there is a server-side component called tiller, that is running in a pod. Yo can t run a pod as a user just as a service account. So if you use helm2 this is the only way. At helm3 there is no tiller. It runs all the actions in the name of the user. So you need to add privileges to the user. If you use groups you can add troth the groups. |
Thank you for the replay and i am using helm 3 and created a name space and given below role and rolebinding to the specific group , but when the user tired to install the cert-manager using helm kind: Role
Error:- kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.8.2/cert-manager.crds.yaml |
RBAC permissions for Helm - devopstales
https://devopstales.github.io/kubernetes/k8s-helm-rbac/
The text was updated successfully, but these errors were encountered: