-
Notifications
You must be signed in to change notification settings - Fork 133
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
When using a context with a namespace that is not default
, pod completion is for default namespace
#13
Comments
Thanks for using kube-prompt. kube-prompt just wraps kubectl like: So It looks that your problem is no relevant to namespace. And your problem is also occurred when just executed following command directly. $ kubectl describe pod canopy-2965694291-f5f6c |
I looked into the code a bit and it seems like the issue is that the completer always uses the default namespace when looking pods (see here) Where as since the executor is shelling out to |
Looks like this was fixed in 49b6437. |
@cgilling - I agree that when working outside of the default context, some of the features provided by kube-prompt break. ex. ">>> -n myNamespace get po" Normally cube-prompt would allow me to tab complete the 'get' verb, and then suggest I've gotten around this by simply setting the default namespace in my context using: Then I can work in my most used namespace and enjoy the creature comforts provided by this very handy tool ;) It sounds like several people here, like me, need to work in multiple namespaces, and this workaround doesn't solve for rapid namespace changes, so I think better namespace support in kube-prompt would be a worth while improvement. Keep up the good work @c-bata ! Cheers |
Hi there! As @carolynvs says, this problem has already fixed at master branch.
So please wait until few weeks later. I promised kube-prompt will be really better from the next release. |
great thanks |
First off, thanks for writing this tool, it looks like it should be pretty helpful. Excited to start using it more.
This is for version 1.0.1:
As you can see below my context is registered to use the
seu
namespace by default, but the completions are from thedefault
namespace. But then when the actual command is run it uses the proper namespace, and therefore can't find my auto completed pod.The text was updated successfully, but these errors were encountered: