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'm facing the following problem with using the flux plugin in our environment:
In our cluster normal users have permissions in their own namespaces and the built-in "View" role on a few platform-level namespaces like "flux-system".
When trying to use the flux plugin they are shown the "Helm Controller is not installed" label.
After analysis of the network calls the api request to /apis/apps/v1/deployments?labelSelector=app.kubernetes.io%2Fpart-of%3Dflux
fails with 403 for these users.
If I'm right this is because this api request is equivalent to kubectl get deployments -A -l app.kubernetes.io/part-of=flux -v8
and the users do not have the permission to get deployments in all namespace.
Instead the users do have the permission to kubectl get deployments -n flux-system -l app.kubernetes.io/part-of=flux -v8
=> apis/apps/v1/namespaces/flux-system/deployments?labelSelector=app.kubernetes.io%2Fpart-of%3Dflux
Probably somebody can give me a pointer where this is in the code? - I was not able to find this code part :/
I think this is a common scenario.
A solution could be to add an configuration option in the Settings > plugins > flux to specify the namespace (here "flux-system") where the flux controllers are installed.