Support KUBECONFIG environment variable #84
Closed
Comments
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
One way of specifying an alternate context for
kubectl
is to set the environment variableKUBECONFIG
to point to a non-default configuration file. Once done, this allows the user to usekubectl
as always to talk to the desired cluster.Telepresence does not respect this environment variable, leading to confusing situations where the telepresence log file shows a
kubectl
command failing whereas the same command typed at the shell completes successfully. Other (worse) failure modes are possible too.The text was updated successfully, but these errors were encountered: