How to predefine KUBECONFIG localion for tsh kube?

[riuvshyn]

Applies To

tsh kube

Details

I am looking for a way to have similar user experience as it used to be with v17 where I could:

• logged in once - session is available for all terminal sessions
• logged in to another cluster it appends kubeconfig so then I can use kubectl --context
• using kubectl without running tsh proxy or tsh kubectl which is very painful

How can I configure teleport client to always use specified KUBECONFIG?

How will we know this is resolved?

Related Issues

[mg1986jp]

In v18+ the kube login flow changed — tsh kube login doesn't directly write to ~/.kube/config by default anymore. You probably want to add this to your shell profile:

export KUBECONFIG=${KUBECONFIG:-$HOME/.kube/config}:$HOME/.tsh/kubeconfig

Then after tsh login && tsh kube login <cluster>, the kube context should be available to plain kubectl without needing tsh proxy or tsh kubectl.

If you're switching between multiple clusters, tsh kube login <cluster> should still append contexts. You can then use kubectl config use-context or --context as usual.

Another approach is eval $(tsh env) which sets up the environment variables for the current session, but that only affects the current shell.