Selected context not respected when checking if namespace exists #787
Labels
Projects
Comments
This issue still exists. Workflows that supply both |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
During startup when checking if the selected namespace exists, the context is not supplied to the
kubectl get ns
command:telepresence/telepresence/startup.py
Line 127 in c6a5e56
That is, it'll use your global context, which not necessarily is the desired context. Reproduce by setting the global context to a cluster without the selected namespace.
I propose the following fix (read: works for me, was broken before): toknapp@571a862
The text was updated successfully, but these errors were encountered: