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.

Sign up for GitHub

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

Jump to bottom

Failure detecting plugins since kubectl v1.26.0 #4

Closed
badouralix opened this issue Dec 12, 2022 · 0 comments · Fixed by #5
Closed

Failure detecting plugins since kubectl v1.26.0 #4

badouralix opened this issue Dec 12, 2022 · 0 comments · Fixed by #5

Comments

@badouralix
Copy link
Owner

badouralix commented Dec 12, 2022 •
edited

kubernetes/kubernetes#105867 introduces plugin names as part of the output of kubectl __completeNoDesc ""
This results in a false negative detecting the requested command is a plugin, leading to the unexpected following error :

Error: flags cannot be placed before plugin name: --context=kind-kind

System info :

$ kubectl version --client --short
Flag --short has been deprecated, and will be removed in the future. The --short output will become the default.
Client Version: v1.26.0
Kustomize Version: v4.5.7
@badouralix badouralix changed the title Failure detecting plugins since kubectl 1.26 Failure detecting plugins since kubectl v1.26.0 Dec 13, 2022
@badouralix badouralix mentioned this issue Dec 13, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update magic to detect native kubectl commands badouralix/kubekeeper
1 participant
@badouralix