No output is displayed when failing about k9s HOT 9 CLOSED

Hi Matthew,

Thank you for reporting back! For non standard kubeconfig location K9s support the env var KUBECONFIG wit the location of your config file. Did you try setting this env var?

I know I need to do more work in the area of configuration and logging but is there anything in /tmp/k9s.log that would indicate the configuration error? If so can you please send me the output and logs?

from k9s.

@derailed That works, but issue still remains that it just fails with no message. A message as to why it exited would be really helpful

from k9s.

@derailed The issue for me was that I have my configs in separate files, so my KUBECONFIG looks something like: export KUBECONFIG=${HOME}/.kube/configs/cluster1:${HOME}/.kube/configs/cluster2 so having the app prompt me to select the context, or add a config value for default context (then I can use ctx<enter> to switch between them) would be great

from k9s.

@alanquillin - Thank you for reporting back! I think the app just blocks trying to contact the api server. I did not test the multiple file scenario in the env var as of yet. I'll take a peek.

from k9s.

@derailed I checked the logs and i see the error "time="2019-02-03T16:36:34Z" level=fatal msg="invalid configuration: [context was not found for specified context: kubernetes-admin@kubernetes, cluster has no server defined]"" and this seems be caused by the same issue as @alanquillin experienced where i am using KUBECONFIG with multiple files.

But i think this is a somewhat separate issue to nothing being printed when an error occurs on startup, i'm happy to open a separate if you think thats better.

from k9s.

@matthewellis Thanks for reporting back. I am getting ready to drop a new rev and added fail early measures so we can actually see what's up.

@alanquillin as far as the multi file in KUBECONFIG (I could be wrong here) but I think once you merge multi file and try to see a current context kubectl does not know which file to set the config to. So I think changing context when using this technic might not work even with kubectl. I'll need to double check...

from k9s.

@derailed So I have my KUBECONFIG setup based on the docs https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/#set-the-kubeconfig-environment-variable using multiple file as I described above, and it works great with kubectl. So my work around currnently is to add everything to my ~/.kube/config file, and you app works great, but that adds an extra step to my work flow.

from k9s.

@alanquillin Thanks for reporting back! You're absolutely correct. There are so many way in K8s to connect to the api server and I think I've found the right incantation this time. Just tried the $KUBECONFIG multi file and I think we're going to be happy on the next drop. Hopefully this will resolve other issues with connectivity too...

from k9s.

Thanks for reporting back! I think this is fixed in 0.1.3

from k9s.