Tab completion breaks if using recommended alias kubectl='minikube kubectl --'

[vcc-huf]

1. install minkube
2. add alias kubectl='minikube kubectl --' to .bashrc
3. add source <(kubectl completion bash) to .bashrc

result:
only the commands get tab-completed, nothing after that.

the underlying issue is this:

$ minikube kubectl __completeNoDesc get p
Error: flags cannot be placed before plugin name: --cluster

this works however:

~/.minikube/cache/linux/v1.22.3/kubectl __completeNoDesc get p

related to this: kubernetes/kubectl#884

[afbjorklund]

You could try making "kubectl" a symlink to "minikube", rather than a bash alias.

[vcc-huf]

found this workaround. put it in bashrc:

KUBECTL_PATH="$HOME/.minikube/cache/linux/$(minikube kubectl -- version -o json | jq -r '.clientVersion.gitVersion')/kubectl"

kubectl() {
    $KUBECTL_PATH "$@"
}

source <(kubectl completion bash)

[vcc-huf]

You could try making "kubectl" a symlink to "minikube", rather than a bash alias.

nah, same problem, minikube starts kubectl with --cluster minikube before the completion stuff, and kubectl cant handle that (see the bug i linked).

[medyagh]

hm.. that seems like a feature it can't do, I would accept a purposal or a PR that would fix or find a work around for this?

we would need to add the --cluster because the user might have multiple clusters and that had caused our tests to fail

[vcc-huf]

well, until they fix kubectl, you can maybe provide an official and supported way to directly call the kubectl installed by minikube?
the one i discovered is rather a hack.

[vcc-huf]

just realized that my hack doesnt work if the minikube node is down... because of reasons.

this does work however:

KUBECTL_PATH="$HOME/.minikube/cache/linux/$(minikube kubectl -- version 2>/dev/null | perl -lne '/GitVersion:"([^"]*)"/ && print $1')/kubectl"

it's even worse though.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[medyagh]

just realized that my hack doesnt work if the minikube node is down... because of reasons.

this does work however:

KUBECTL_PATH="$HOME/.minikube/cache/linux/$(minikube kubectl -- version 2>/dev/null | perl -lne '/GitVersion:"([^"]*)"/ && print $1')/kubectl"

it's even worse though.

@vcc-huf is this a good work arround ? if yes you could add it to our website as a tip for other users

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[oldium]

Same on Windows actually. The command minikube kubectl is broken with regards to autocomplete (i.e. command __complete) in PowerShell too.

[oldium]

Maybe it would be sufficient to update the following line to simply accept __complete in the same way as --help:

minikube/cmd/minikube/cmd/kubectl.go

Line 99 in 8d34afd

if len(args) > 1 && args[0] != "--help" {

[oldium]

Created PullRequest with the fix, now the __complete request is passed as-is to kubectl.

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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.

[vipseixas]

just realized that my hack doesnt work if the minikube node is down... because of reasons.

this does work however:

KUBECTL_PATH="$HOME/.minikube/cache/linux/$(minikube kubectl -- version 2>/dev/null | perl -lne '/GitVersion:"([^"]*)"/ && print $1')/kubectl"

it's even worse though.

I had to change this a little to work:

KUBECTL_PATH="$HOME/.minikube/cache/linux/amd64/$(minikube kubectl -- version --client 2>/dev/null | perl -lne '/GitVersion:"([^"]*)"/ && print $1')/kubectl"