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

Selected context not respected when checking if namespace exists #787

Closed
rootmos opened this Issue Sep 25, 2018 · 1 comment

Comments

3 participants
@rootmos

rootmos commented Sep 25, 2018

During startup when checking if the selected namespace exists, the context is not supplied to the kubectl get ns command:

runner.get_output([prelim_command, "get", "ns",

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

@kooba

This comment has been minimized.

kooba commented Nov 23, 2018

This issue still exists. Workflows that supply both --context and --namespace and don't have current-context set in kube/config do not work at the moment and error T: Error: Namespace 'mynamespace' does not exist is raised.

@ark3 ark3 added the bug label Nov 23, 2018

@ark3 ark3 added this to To do in Tel Tracker via automation Nov 23, 2018

ark3 added a commit that referenced this issue Nov 23, 2018

@ark3 ark3 closed this in #843 Nov 23, 2018

Tel Tracker automation moved this from To do to Done Nov 23, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment