-
-
Notifications
You must be signed in to change notification settings - Fork 100
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
Role and RoleBinding support #305
Comments
This could be solved by #314 maybe? |
Not really, as I'm not talking about app-template, just about the common library. I'm anyway writing own chart using the library so I can add role myself using normal templates. Roles are pretty much common tho so I was thinking that adding those to the library for ease of use would be cool. |
I'm definitely open to adding it, I'm just not sure (yet) what the cleanest way of exposing it through the roles:
blah:
clusterWide: false
rules:
- apiGroups:
- ""
resources:
- pods
verbs:
- get
roleBindings:
blah:
clusterWide: false
roleRef:
kind: Role
identifier: blah
# name: optional role name instead of identifier
subjects:
- kind: User
name: bjw-s |
If you want to allow multiple roles and bindings, maybe you should also consider multiple serviceaccounts support |
While maybe true, I don't think I could easily add that without breaking changes. I'll take a look at it |
I have a Role/Rolebinding implementation in my fork, I could create a PR if you want. This would be the values.yaml structure:
It would be nice to add multiple ServiceAccount support as well to make it easier to add it in the roles (I'm working on that in my fork, but can't find an elegant way of integrating it with the pods, I'll update if I can think of anything interesting) |
@LarryGF I also want to use roles/rolebinding but can't find it in your forked repo. Would you mind sharing it please. |
Details
Describe the solution you'd like:
Support for creating Role and assigning this role to ServiceAccount using RoleBinding
Additional Information:
This is handy with some pre-install/pre-upgrade jobs initializing secrets/configMaps
The text was updated successfully, but these errors were encountered: