-
Notifications
You must be signed in to change notification settings - Fork 8
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
Default release namespace for namespaced rbac #579
Default release namespace for namespaced rbac #579
Conversation
Issues linked to changelog: |
Instead of altering these templates, why don't we just set defaults in GME's gloo-platform helm chart? Default being the 3 resources we need along with the release namespace for glooUi.namespacedRbac. |
We can't set the release namespace by default in the gloo-platform helm chart - see https://github.com/solo-io/gloo-mesh-enterprise/issues/15739#issuecomment-2313169671 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
Description
In https://github.com/solo-io/gloo-mesh-enterprise/pull/17198, we added Pods, ConfigMaps, and Secrets to the DashboardInputSnapshot, which caused the gloo-mesh-ui to begin reading all of these resources from all namespaces in the mgmt-cluster. We intended to only allow these resources to be read from the 'gloo-mesh' namespace, but the NamespacedRbac requires you to pass in glooUi.namespacedRbac values in order to activate that feature.
By default, we want to set the glooUi.namespacedRbac.resources values, and no glooUi.namespacedRbac.namespaces value. Then we want to make a skv2 change so that if glooUi.namespacedRbac.namespaces is empty but glooUi.namespacedRbac.resources is not, we default to the Release.Namespace.
BOT NOTES:
resolves https://github.com/solo-io/gloo-mesh-enterprise/issues/15739