The error for "unset $KUBECONFIG" is needlessly cryptic

[curusarn]

Forgetting to set $KUBECONFIG results in a following error:

❯ tk diff envs/name
connecting to Kubernetes: finding usable context: expected clusters to be of type `[]map[string]interface{}`, but got `<nil>` instead

This is imho a pretty common mistake among newcomers so it would make sense to handle unset $KUBECONFIG as a separate error.

What do you think?

[captncraig]

I agree.. sort of? $KUBECONFIG not being set will default to the system default ($HOME/.kube/config or something), but if that is absent, yeah, probably makes sense to tell them we couldn't find anything.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[curusarn]

I'm willing to submit a PR fixing this if maintainers agree that it is a good idea.

[Duologic]

Sounds reasonable to me, a nice hint could help a newcomer definitely.