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.

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

Tenant RBAC enhancement #79

Open
venkatesh-mb opened this issue Jun 23, 2022 · 3 comments
Open

Tenant RBAC enhancement #79

venkatesh-mb opened this issue Jun 23, 2022 · 3 comments

Comments

@venkatesh-mb
Copy link

Is there any example that we can extend tenant role bindings to apply cluster level?

We have a use case where my ingress controller have some cluster level roles and bindings which are not possible to apply with existing tenant role bindings.

Can you suggest how can we go with this issue?

@stefanprodan
Copy link
Member

Place the ingress controller Flux HelmRelease or Flux Kustomization in the flux-system namespace and set the service account to either helm-controller or kustomize-controller. Or you could create a dedicated tenant for cluster admins, where you would modify the RoleBinding to be a ClusterRoleBinding.

@venkatesh-mb
Copy link
Author

Thanks @stefanprodan . We have followed the same way for deploying cluster level tools. But we have some other applications which we want to go with tenant level. Yes, i am thinking of creating a new tenant create new service account but i am having difficulty what set of RBAC we should give it that tenant to have access to apply changes at cluster role.

@stefanprodan
Copy link
Member

As I said change the RoleBinding into a ClusterRoleBinding here https://github.com/fluxcd/flux2-multi-tenancy/blob/main/tenants/base/dev-team/rbac.yaml#L20

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants