Documentation for user impersonation via kubeconfig

[aljoshare]

This is a Feature Request

What would you like to be added
Currently, only the impersonation of users via headers and kubectl flags is documented. It would be helpful to also explain and describe the possibility to configure user impersonation via kubeconfig.

Why is this needed
Its sometimes helpful to configure the user impersonation via kubeconfig, e.g. for external tooling (Example: istio/istio#22365 (comment)) but currently you need to know that it is possible and check the API spec for further information.

Comments

• Allow impersonating a Kubernetes user/group with istioctl istio/istio#22365 (comment))
• https://github.com/kubernetes/client-go/blob/b69cda3e4e09e1b956d42709fbadf12e6c0f24b7/tools/clientcmd/api/types.go#L131-L140

[sftim]

There's a reference at https://kubernetes.io/docs/reference/config-api/kubeconfig.v1/

Are you looking for a task page that explains how to set up a kubeconfig for accessing a single cluster? We don't yet have one of those.
I'll file an issue.

[aljoshare]

I would love to see a short example as part of the user impersonation section in the docs. There is an example for kubectl and a general description of the headers but there is no example for it via kubeconfig.

https://kubernetes.io/docs/reference/access-authn-authz/authentication/#user-impersonation

[sftim]

If we add the page that #38681 calls for, https://kubernetes.io/docs/reference/access-authn-authz/authentication/#user-impersonation could link there.

I like hyperlinks - it's easier to maintain pages when we write content once and link to it, than if we duplicate.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[sftim]

/lifecycle frozen
/triage accepted
/remove-lifecycle rotten
/priority backlog

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted