Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Support for KUBECONFIG

See original GitHub issue

kubectl uses the KUBECONFIG environment variable. It would be great if kube-shell would honor it as well.

About KUBECONFIG: https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/#set-the-kubeconfig-environment-variable

Current behavior:

 ~> kube-shell
Kube-shell uses ~/.kube/config for server side completion. Could not find ~/.kube/config. Server side completion functionality may not work.
kube-shell>

Expected behavior:

kube-shell follows path(s) as defined in $KUBECONFIG.

Issue Analytics

State:
Created 6 years ago
Reactions:10
Comments:6 (1 by maintainers)

Top GitHub Comments

1reaction

damomurfcommented, Feb 22, 2018

kubectl can actually function perfectly well if the value of KUBECONFIG is also a list of kubectl config files, not necessarily just one. It would be ideal if this tool could support that use case too.

0reactions

b1xcommented, Jun 24, 2018

@murali-reddy, I am sorry but I can’t switch context when I use variable KUBECONFIG, like: export KUBECONFIG=${HOME}/.kube/first:${HOME}/.kube/second It always on first(