Open
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
The command kubectl auth can-i --as=some-user --as=some-group
does not give correct results. It always gives the result for the currently (actually) authenticating user.
The cause is most possibly because the way we proxy the requests over Omni to Kubernetes: we ignore the impersonation headers: https://kubernetes.io/docs/reference/access-authn-authz/authentication/#user-impersonation
We should either implement impersonation (careful with the privilege escalation!) or at least return an error saying we don't support it.
Expected Behavior
The command giving correct results.
Steps To Reproduce
- Be admin.
- Run any
kubectl auth can-i --as=...
command. - See
yes
as the result.
What browsers are you seeing the problem on?
No response
Anything else?
No response