Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kubectl debug autocompletion isn't working #1711

Open
dprotaso opened this issue Feb 7, 2025 · 4 comments · May be fixed by kubernetes/kubernetes#130033
Open

kubectl debug autocompletion isn't working #1711

dprotaso opened this issue Feb 7, 2025 · 4 comments · May be fixed by kubernetes/kubernetes#130033
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/cli Categorizes an issue or PR as relevant to SIG CLI. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@dprotaso
Copy link
Contributor

dprotaso commented Feb 7, 2025

What happened?

Autocompletion for kubectl debug doesn't look up the pod name

What did you expect to happen?

I expected the pod name to be looked up similar to kubectl get -n [namespace]

How can we reproduce it (as minimally and precisely as possible)?

Create a pod in some namespace (x)

type
kubectl debug -n x

then hit tab and notice the pod name doesn't autocomplete

Anything else we need to know?

zsh 5.9 (arm64-apple-darwin24.0)

Kubernetes version

$ kubectl version
Client Version: v1.32.1
Kustomize Version: v5.5.0
Server Version: v1.32.0

Cloud provider

N/A

OS version

MacOS 15.3

Install tools

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

@dprotaso dprotaso added the kind/bug Categorizes issue or PR as related to a bug. label Feb 7, 2025
@k8s-ci-robot k8s-ci-robot added needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 7, 2025
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@dprotaso
Copy link
Contributor Author

dprotaso commented Feb 7, 2025

/sig cli

@k8s-ci-robot k8s-ci-robot added sig/cli Categorizes an issue or PR as relevant to SIG CLI. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Feb 7, 2025
@Ruchi1499
Copy link

I tested the kubectl debug -n <namespace> command, and found that tab auto-completion isn't working as expected. Instead of showing valid completions, it lists local files and directories, such as:

Image

@ardaguclu
Copy link
Member

/transfer kubectl
/triage accepted
/priority backlog
/assign

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/backlog Higher priority than priority/awaiting-more-evidence. labels Feb 7, 2025
@k8s-ci-robot k8s-ci-robot transferred this issue from kubernetes/kubernetes Feb 7, 2025
@k8s-ci-robot k8s-ci-robot removed the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/cli Categorizes an issue or PR as relevant to SIG CLI. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Status: Needs Triage
Development

Successfully merging a pull request may close this issue.

4 participants