microsoft / microsoft/vscode-remote-release

User impersonation with kubectl "--as argument"

Open
#11,465 0 comments 0 reactions 1 assignee View on GitHub

@chrmarti is already working on this.

Since Jan 28, 2026.

containers feature-request
Dominant language
Dockerfile
Stars
4.2k
Forks
469
Avg merge
1d 1h
Merged PRs (30d)
1

Description

In our Kubernetes cluster, we use Pinniped (https://pinniped.dev/) for access control. This makes access to the cluster a lot more strict and requires that the user pass in a "--as" argument to kubectl. For example:

kubectl get pods --as <some-admin-user-name>

Without the --as argument, the call to kubectl is denied. This can be worked around by adding the line:

as: <some-admin-user-name>

To the kubeconfig file, but this does not work well as the user name is different for different namespaces and adding as: to the kubeconfig is a global cluster setting.

It would be very useful to be able to configure the VS Code Dev Container extension to specify the user to be passed to the --as parameter, and to have the extension use this parameter when calling kubectl. This setting should be able to be made on a per-namespace basis.

I would add this functionality myself, but the Dev Container extension is not open source (I have added the functionality to the VS Code Kubernetes extension, which is open source).

This is the error that we currently get in VS Code:

Unable to use a TTY - input is not a terminal or the right kind of file Error from server (Forbidden): pods "my-pod-8f8f868bd-mglbd" is forbidden: User "redacted@redacted.com" cannot create resource "pods/exec" in API group "" in the namespace "my-namespace": decision made by impersonation-proxy.concierge.pinniped.dev

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.