Include vs-kubernetes/tools/kubectl in path.

By using the official Kubernetes extension (_ms-kubernetes-tools.vscode-kubernetes-tools_), Visual Studio Code can automatically install binaries for kubectl, helm, and minikube.

Unfortunately, if you attempt to explore workloads and try to attach vscode to a running pod, you encounter the following error:

**Error running command remote-containers.attachToK8sContainerFromViewlet: A system error occurred (spawn kubectl ENOENT). This is likely caused by the extension that contributes remote-containers.attachToK8sContainerFromViewlet.**

To fix this issue, you can edit code.sh (line 67) by adding the following path:

**${XDG_DATA_HOME}/.local/state/vs-kubernetes/tools/kubectl**

After making this change, vscode is able to find the kubectl binary and the extension will be fully functional.

Open code.sh and inspect line 67, then compare the PATH entries with the kubectl location installed by the Kubernetes extension. Include the requested vs-kubernetes/tools/kubectl path and verify that VS Code can find kubectl when attaching to a running pod.

Vom Indexierungsmodell aus dem Issue-Text verfasst.