-
Notifications
You must be signed in to change notification settings - Fork 80
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
Error: failed to get namespace of current context: context with name "/Users/userid/.kube/config" not found #32
Comments
Probably nothing as this is possibly a bug. It seems to be related to the recently introduced namespace switching functionality. Does |
Also you could post a sanitized version of this kubeconfig + your switch-config.yaml |
after the run Not working: `switch -d , the context doesn't get deleted.
Works only if I run
the kubeconfig is quite a default configuration without any directories and for some reason switch-config.yaml is not even present in the
|
ok thanks, just wanted to check if there is any custom config present.
That is expected as switch -d only works on the local copy of the kubeconfig file. So in your case , the context is only deleted from the temporary file, not the original kubeconfig. I ll have a look at that namespace issue, sorry for the inconvenience. |
thanks for the fix
both of these 2 commands are working now!
are you going to look into this?
|
What is the problem here? For the output I can see that the context was removed - mind you, removed from the temporary kubeconfig file. It will not be removed from the original kubeconfig file. |
@danielfoehrKn thanks! |
Just released version 0.6.2 which includes the fix - thanks again for reporting. Feel free to open again if you come across the issue again. |
when I run only
switch
, the context is listed without issue.What I'm doing wrong ?
The text was updated successfully, but these errors were encountered: