Completion for kubectl plugins

[weibeld]

FEATURE REQUEST

Kubernetes version (use kubectl version): 1.13

Environment:

• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release): macOS 10.14
• Kernel (e.g. uname -a): Darwin Kernel Version 18.2.0: Mon Nov 12 20:24:46 PST 2018; root:xnu-4903.231.4~2/RELEASE_X86_64

What happened:

Having installed a kubectl plugin kubectl-test:

$ kubectl t[tab][tab]
taint top

You can't complete plugin commands as you can complete built-in commands.

What you expected to happen:

$ kubectl t[tab][tab]
taint test top

$ kubectl te[tab]  # Completes to 'kubectl test'

Anything else we need to know:

Completion for plugin names could be implemented in the kubectl completion script. But completion for arguments of plugins are plugin-dependent and can't be implemented in the kubectl completion script. In this case, plugin creators could provide completion scripts for their plugins which can then be invoked by the kubectl completion script when it detects that the user is using a plugin command.

[seans3]

/sig cli
/area kubectl
/kind feature

[superbrothers]

I try to implement completion for kubectl plugins.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[weibeld]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[weibeld]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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/test-infra repository.