microsoft / microsoft/vscode-remote-release
Attach to kubernetes: Support alternate config files
Open
@chrmarti is already working on this.
Since Apr 5, 2022.
bug
containers
kubernetes
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Attaching to Kubernetes container does not work if using different Kubernetes configuration other than default. Listing and describing containers work as expected
- VSCode Version: 1.64.2 (Universal), Commit: f80445acd5a3dadef24aa209168452a3d97cc326
- Local OS Version: MacOS Big Sur
- Remote OS Version: Kubernetes 1.22, Alpine container
- Remote Extension/Connection Type: Kubernetes
- Logs:
Error running command remote-containers.attachToK8sContainerFromViewlet: Command failed: kubectl config current-context. This is likely caused by the extension that contributes remote-containers.attachToK8sContainerFromViewlet.
Steps to Reproduce:
mv ~/.kube/config ~/kube/config-staging- Add config-staging to VSCode
- Chose any container and try to
Attach Visual Studio Code - Get the error above
mv ~/kube/config-staging ~/.kube/config- Attach to container successfully
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.