-
Notifications
You must be signed in to change notification settings - Fork 488
feat(helm): add support for rbac at namespace scope #1698
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
Conversation
- add boolean field namespaceScoped to values.yaml to enable creation of role and rolebinding - update helm chart generation script and manifest bundle to handle creation of rbac at cluster or namespace level depending on user input - updated manifest builder script to generate rbac for namespace level Signed-off-by: dashashutosh80 <dashashutosh80@gmail.com>
419cf20
to
02a7d82
Compare
@Slach Please review the updated changes and let me know if anything else needs to be done. Thanks in advance! |
@dashashutosh80 any news from your side? could we stay ClusterRole default behavior? |
@Slach sorry I have been afk for a while now. I’ll update the values.yaml and readme with cluster Role as default behavior in 2-3 days. |
@dashashutosh80 any news from your side? |
@Slach Updated the values.yaml to keep namespace scoping of rbac disabled by default until user overwrites. This should not break installations during upgrade where kube-system is set as namespace and operator already runs with cluster level permissions. Please take a look |
next-release
branch, not intomaster
branch1. More infoThis PR contains the following changes:
This PR aims to address #1423