k9s: "Shell exec failed" on 0.26.4 to 0.26.6 Windows OS

Describe the bug A clear and concise description of what the bug is.
Shell does not start on version 0.26.4 to 0.26.6 on Windows from a pod.
To Reproduce Steps to reproduce the behavior:
- On Windows, use K9s 0.26.4 to 0.26.6
- Use
<s>
on a pod to start a shell - See error “Shell exec failed”
Expected behavior A clear and concise description of what you expected to happen.
Shell should be started. It fails with “Shell exec failed”.
Versions (please complete the following information):
- OS: Windows
- K9s: 0.26.4 to 0.26.6, WORKS on 0.26.3 and
kubectl exec -it pod -- /bin/bash
- K8s: 1.22.12
Additional context Add any other context about the problem here.
Works on 0.26.3. Does not work on 0.26.4 to 0.26.6.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 25 (5 by maintainers)
Commits related to this issue
- fix: Show meaningful error message when kubectl exec fails (#1966) `exec.LookPath()` and `exec.Command()` aren't supposed to work with binaries that are located in the current working directory: ... — committed to derailed/k9s by AntonioND a year ago
- Updating personal fork (#3) * wins palette * Add Nord skin (#1103) * fix bugz * when k9s --insecure-skip-tls-verify is set, kubectl would set the same (#1101) * when k9s --insecure-skip-t... — committed to agrimrules/k9s by agrimrules a year ago
scoop install kubectl
is a solution for me.