You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've continued to dig and also user must be able to get Flux resources (Kustomization, HelmRelease, ...) at cluster level, even if a namespace is given (and same here, our users doesn't have this right)
On the "base" headlamp, different resources are namespace scoped if a namespace is provided
Hello,
today Flux plugin mandates that all the users are allowed to list deployments at cluster scope. And in our case, only admins are allowed to do that.
Looking (rapidly) at the code, it seems it's only needed for runtime checks but not for the other pages.
Is there a need I haven't seen?
Otherwise, do you think it could be feasible to remove such constraint?
Thanks!
Sylvain
The text was updated successfully, but these errors were encountered: