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

[Flux] Use plugin without access to flux deployed namespace #161

Open
sylvainOL opened this issue Feb 12, 2025 · 1 comment · May be fixed by #165
Open

[Flux] Use plugin without access to flux deployed namespace #161

sylvainOL opened this issue Feb 12, 2025 · 1 comment · May be fixed by #165
Labels
bug Something isn't working flux flux plugin related issues

Comments

@sylvainOL
Copy link

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

@sylvainOL
Copy link
Author

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

@illume illume added bug Something isn't working flux flux plugin related issues labels Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working flux flux plugin related issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants