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
Broken kubectl completion with override flags #80797
Comments
k8s-ci-robot
added
the
needs-sig
Indicates an issue or PR lacks a `sig/foo` label and requires one.
label
Jul 31, 2019
/sig cli |
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
Jul 31, 2019
I also reproduced this bug with the following steps:
|
I'm fixing it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened:
With kubectl v1.16.0-alpha.2, completion with override flags fails.
kubectl --kubeconfig=foo -n
then hit TAB will produce error "resource type must be specified"What you expected to happen:
It must show the namespaces without error.
How to reproduce it (as minimally and precisely as possible):
With kubectl v1.16.0-alpha.2,
kubectl --kubeconfig=foo -n
then hit TAB key.Anything else we need to know?:
It looks like #70470 introduced this regression.
Environment:
kubectl version
): kubectl v1.16.0-alpha.2cat /etc/os-release
):uname -a
):The text was updated successfully, but these errors were encountered: