Start in context view if current-context is empty

[pdecat]

Is your feature request related to a problem? Please describe.

Since minikube v1.1.0, minikube stop unsets the current-context after completion: kubernetes/minikube#4177

When minikube is stopped there's no way to start k9s without changing the current context in kubeconfig:

# kubectl config current-context
minikube

# minikube stop
✋  Stopping "minikube" in kvm2 ...
🛑  Node "minikube" stopped.

# kubectl config current-context
error: current-context is not set

# grep current-context ~/.kube/config
current-context: ""

# k9s
 ____  __.________
|    |/ _/   __   \______
|      < \____    /  ___/
|    |  \   /    /\___ \
|____|__ \ /____//____  >
        \/            \/

Boom!! Invalid kubeconfig context detected.

Passing -c ctx to start in context view does not help:

# k9s -c ctx
 ____  __.________
|    |/ _/   __   \______
|      < \____    /  ___/
|    |  \   /    /\___ \
|____|__ \ /____//____  >
        \/            \/

Boom!! Invalid kubeconfig context detected.

Describe the solution you'd like

It would be awesome if k9s would start in context view when the current-context is unset instead of exiting.

Describe alternatives you've considered

Submit a feature request to minikube to allow opting-out of removing the current context from kubeconfig on stop.

Additional context

N/A

[derailed]

@pdecat Thanks Patrick! Please checkout v0.21.3

[pdecat]

Awesome, works perfectly now!

Thanks @derailed!