Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support KUBECONFIG environment variable #84

ark3 opened this issue Apr 4, 2017 · 0 comments

Support KUBECONFIG environment variable #84

ark3 opened this issue Apr 4, 2017 · 0 comments


Copy link

@ark3 ark3 commented Apr 4, 2017

One way of specifying an alternate context for kubectl is to set the environment variable KUBECONFIG to point to a non-default configuration file. Once done, this allows the user to use kubectl 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.

@itamarst itamarst closed this in #85 Apr 4, 2017
itamarst added a commit that referenced this issue Apr 4, 2017

Fixes #84.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant