helm/v2-alpha: disable cluster wide rbac resource creation #5504
Description
What do you want to happen?
In some multi-tenant Kubernetes environments the user cannot load the ClusterRoles and ClusterRoleBindings during normal deployment. In this case we side-load them via a different process before the actual helm deployment. For this to be possible we should have a feature flag (enabled by default) that allow the use to choose whether to load these resources while deploying the helm release.
For allowing the operator to still be able to manage resources at namespace level a local rb should bind the operator serviceaccount to the clusterRole deployed outside of this chart (by a cluster admin) with then name being configurable.
Extra Labels
No response