-
Notifications
You must be signed in to change notification settings - Fork 2k
Allow helm chart to support external cluster level RBAC #5228
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
Comments
Hi @hafe thanks for reporting! Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂 Cheers! |
6 tasks
Hi @hafe, could you please add the documentation for this feature? |
Sure, exactly where do you mean? |
For example: Add the configuration on helm installation - Configuration |
hafe
added a commit
to hafe/kubernetes-ingress
that referenced
this issue
May 21, 2024
hafe
added a commit
to hafe/kubernetes-ingress
that referenced
this issue
Jun 3, 2024
hafe
added a commit
to hafe/kubernetes-ingress
that referenced
this issue
Jun 6, 2024
Thanks @hafe! |
This was referenced Mar 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
The helm chart comes with a ClusterRole and a ClusterRoleBinding. The ClusterRoleBinding gives very wide access to the whole cluster for example read access to every secret in the cluster. This does not align well with function provided by the -watch-secret-namespace option.
Describe the solution you'd like
A simple knob to disable the cluster level RBAC resource generation from the helm chart. This gives users a way to provide more suited cluster level RBAC externally yet use the upstream helm chart.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: