What happened:
When using the fish completions kubectl debug suggests resource types (e.g., pods). Once pods is accepted, pod names are suggested. However, the resulting command is not valid, instead it should just be kubectl debug <pod-name>
What you expected to happen:
After kubectl debug suggest pod names.
How to reproduce it (as minimally and precisely as possible):
Run kubectl completion fish | source in fish (or have it in your completions directory), then type kubectl debug . Hit tab.
Anything else we need to know?:
Tried on fish 4.8.0. It's still a useful suggestion after deleting pods manually.
Environment:
- Kubernetes client and server versions (use
kubectl version): Client 1.36.2, server 1.34.4
- Cloud provider or hardware configuration: should not be not relevant
- OS (e.g:
cat /etc/os-release): WSL2 Arch Linux
What happened:
When using the fish completions
kubectl debugsuggests resource types (e.g.,pods). Oncepodsis accepted, pod names are suggested. However, the resulting command is not valid, instead it should just bekubectl debug <pod-name>What you expected to happen:
After
kubectl debugsuggest pod names.How to reproduce it (as minimally and precisely as possible):
Run
kubectl completion fish | sourcein fish (or have it in your completions directory), then typekubectl debug. Hit tab.Anything else we need to know?:
Tried on fish 4.8.0. It's still a useful suggestion after deleting
podsmanually.Environment:
kubectl version): Client 1.36.2, server 1.34.4cat /etc/os-release): WSL2 Arch Linux