Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Generate Tailored Roles and RoleBindings for Target Namespaces #522

Closed
csviri opened this issue Mar 3, 2023 · 1 comment
Closed

Generate Tailored Roles and RoleBindings for Target Namespaces #522

csviri opened this issue Mar 3, 2023 · 1 comment
Assignees
@csviri
Labels
enhancement New feature or request

Comments

@csviri
Copy link
Contributor

csviri commented Mar 3, 2023 •
edited
Loading

Currently always a cluster role is generated for the controller. This is a problem when the user who deploys the operator does not have permission to create ClusterRole.

In case quarkus.operator-sdk.namespaces is set, we could generate roles and rolebindings for every namespace listed there.
Althoug service account will live just in the deployment namespace.
@csviri csviri added the enhancement New feature or request label Mar 3, 2023
@csviri csviri self-assigned this Mar 3, 2023
@csviri csviri changed the title Generate Tailored Roles and ClusterRoles Generate Tailored Roles and RoleBindings for Target Namespaces Mar 3, 2023
@metacosm metacosm mentioned this issue Jul 10, 2023
Closed
@csviri
Copy link
Contributor Author

csviri commented Aug 8, 2023

We agreed that this will be done using a Helm chart, see: #668

@csviri csviri closed this as completed Aug 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@csviri csviri

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@csviri