attach to kubernetes pod fails in vscode as context does not exist in the session

Question

We are connecting to kubernetes cluster hosted in AWS. I am able to do it via cli

aws sso login --profile 234234293-prj_ns_qa_manager

#set the context to appropriate sandbox cluster

kubectl config use-context qasandbox1-qa_manager

After this i am to install helm chart in the kubernetes cluster. Also i am able to access pod via cli.

I have install vscode kubernetes extension. I am able to see the cluster and pod .When i attach vscode it opens in another session where this kubernetes context and cluster not found so it throws error as below.

[660 ms] Start: Run: kubectl exec -it my-debug-proj-cli-w7vng --context qasandbox1-qa_manager --namespace qa-manager --container proj-cli -- env VSCODE_REMOTE_CONTAINERS_SESSION=abb319e7-e9f2-4f8f-889c-b1183738e93f1753247958353 /bin/sh
[681 ms] Start: Run in container: echo $PATH
[815 ms] Shell server terminated (code: 1, signal: null)

error: context "qasandbox1-qa_manager" does not exist

How to attach to container in a pod with proper context? or is there a way to open container in the same session where i have configured context?

Samselvaprabu · Accepted Answer · 2025-08-19 13:09:30Z

0

I found the answer recently , I am adding this for other's benefit

Go to Files-> Preferences -> settings -> Vs-kubernetes -> Edit in settings.json

add kubectl path

"vs-kubernetes.kubectl-path": "/usr/local/bin/kubectl",

I am using wsl ,so also enable below settings

After this I am able to attach to a pod

answered Aug 19 at 13:09

Samselvaprabu

18.5k37 gold badges165 silver badges243 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

attach to kubernetes pod fails in vscode as context does not exist in the session

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related