-
Notifications
You must be signed in to change notification settings - Fork 550
K8S user impersonation #2355
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
Comments
This is really important and has to be addressed |
Happy to review PRs if you want to add this. |
cjihrig
added a commit
to cjihrig/javascript
that referenced
this issue
Apr 15, 2025
This commit adds support for username impersonation. This does not implement group, UID, or extra impersonation. Refs: kubernetes-client#2355
cjihrig
added a commit
to cjihrig/javascript
that referenced
this issue
Apr 16, 2025
This commit adds support for username impersonation. This does not implement group, UID, or extra impersonation. Refs: kubernetes-client#2355
cjihrig
added a commit
to cjihrig/javascript
that referenced
this issue
Apr 16, 2025
This commit adds support for username impersonation. This does not implement group, UID, or extra impersonation. Refs: kubernetes-client#2355
The issue and PR are being discussed in more detail in the PR (for visibility). |
cjihrig
added a commit
to cjihrig/javascript
that referenced
this issue
Apr 19, 2025
This commit adds support for username impersonation. This does not implement group, UID, or extra impersonation. Refs: kubernetes-client#2355
Closed by #2373 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
This k8s client doesn't allow impersonating another user/SA in a cluster.
kubectl
binary allows doing this via--as
flag or adding the following entity to kubeconfig:users.user.as
. Even adding the entity to kubeconfig,Client Version
1.1.0
Server Version
1.30.10
To Reproduce
Steps to reproduce the behavior:
Run the following code.
The above code snippet doesn't show the
users.user.as
field even if it's added to the kubeconfig. As well as the client ignores the field when making a request to K8S API.Kubeconfig snippet example:
Expected behavior
It's expected that
as
field is available and can be used to impersonate user in k8s cluster.Example Code
Environment (please complete the following information):
Additional context
Link to k8s doc https://kubernetes.io/docs/reference/access-authn-authz/authentication/#user-impersonation
Link to kubeconfig api reference https://kubernetes.io/docs/reference/config-api/kubeconfig.v1/#AuthInfo
The text was updated successfully, but these errors were encountered: