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

[feature request] display which cluster (context) and namespace currently being viewed #98

Closed
himslm01 opened this issue Jun 10, 2020 · 9 comments · Fixed by #99
Closed
Labels
enhancement New feature or request

Comments

@himslm01
Copy link

After two days of using Kubenav on desktop and tablet I'm really enjoying the UI - especially on an iPad.

But I'd really like to have the context and namespace I'm currently interacting with displayed all the time.

I've currently got 11 contexts registered, each has several namespaces.

I was on a call today looking at resource usage in a pod and I was asked "which environment is that?" Without navigating away from the data I was reading I had no way of telling.

Looking for work-arounds I noticed that:

On the desktop: the "Clusters" drop-down menu doesn't have a check mark next to the currently used context

On the tablet: I really have no way (that I've seen) of seeing which context I'm interacting with unless I go all the way to the "Clusters" menu.

On the desktop and tablet: when you're look at an object's details the menu for changing namespaces (which does have a check mark - when you can see the menu) is not available.

In order to use Kubenav with confidence I believe the user should have feedback about the context and namespace they are currently working in.

Thank you :-)

@si458
Copy link
Contributor

si458 commented Jun 10, 2020

The way I know which namespace I’m working in is I select the settings icon on the top right of any of the tabs say ‘pods’ and it shows a tick next to which namespace I’m viewing including ‘show all’ which then shows a grey name on top of your items being listed so you know which belong to which

As for which cluster you browsing, I can’t help there as I only have a single cluster sorry

@ricoberger ricoberger added the enhancement New feature or request label Jun 10, 2020
@ricoberger
Copy link
Member

Hi @himslm01, I like the idea to improve the visibility of the current context. I already started some time ago with this or better with the improvement of the context switching.

I committed my ideas and created #99. Your feedback would be very useful. You can download the build for this PR from https://github.com/kubenav/kubenav/actions/runs/131370304

@si458
Copy link
Contributor

si458 commented Jun 10, 2020

@ricoberger just tried it and wow that easy!
i created a minikube cluster so i now have 2 to switch between
any chance of maybe adding a namespace switcher underneath the context switcher rather than the namespace switcher being inside the settings button on top right?

@ricoberger
Copy link
Member

Thanks for the fast feedback, I will look into this.

@himslm01
Copy link
Author

Hi @ricoberger. On Linux when I download the build from that PR I get a Zip, containing a tar.gz, containing one file - the kubenav executable. What do I do to make it run?
I tried replacing the kubenav executable in the previous install - leaving the electron framework around it - but I didn't notice any difference. Sorry to be thick.

@ricoberger
Copy link
Member

Hi @himslm01, it should be enough when you start the executable via double click. Then it should be create two folders vendor and resources. It's not necessary to keep the old installation, because I changed the underlying architecture some time ago.

If kubenav doesn't start you can also start it via terminal, there you are also getting an error message in case it doesn't work.

@himslm01
Copy link
Author

Hi @ricoberger,
Thanks.. I ran kubenav in an empty folder from the command line:

$ ./kubenav 
INFO[0000] (version=, branch=HEAD, revision=85795a5c228bab853dddff09eee6a7ec0c2c53eb) 
INFO[0000] (go=go1.14.4, user=runner, date=2020-06-10@19:34:16) 
INFO[0000] Version Check: Current , Available 1.4.1     
FATA[0000] Could not create menu                         error="stat /home/mdsh/.kube/config:/home/mdsh/.kube/config.d/home/config:/home/mdsh/.kube/config.d/bbc/config: no such file or directory"
mdsh@caspar001:~/Applications/tmp$ env|grep KUBE
KUBECONFIG=/home/mdsh/.kube/config:/home/mdsh/.kube/config.d/home/config:/home/mdsh/.kube/config.d/bbc/config

Do you want me to make a new ticket for parsing the KUBECONFIG environment variable correctly?
Kubenav runns as expected if I reduce my KUBECONFIG to one file

$ KUBECONFIG=/home/mdsh/.kube/config.d/home/config ./kubenav
INFO[0000] (version=, branch=HEAD, revision=85795a5c228bab853dddff09eee6a7ec0c2c53eb) 
INFO[0000] (go=go1.14.4, user=runner, date=2020-06-10@19:34:16) 
INFO[0000] Version Check: Current , Available 1.4.1     
INFO[0000] astikit: starting worker...                  
INFO[0004] astikit: worker is now waiting...

Yes, I really like the Context drop-down-menu. It appears (to my mind) in a slightly strange place at the bottom middle of the window - a long way from the menu, but I'm sure I can get used to that :-)

@ricoberger
Copy link
Member

Thanks for your feedback.

Yes a new ticket for the parsing of the KUBECONFIG environment variable would be good.

@ricoberger
Copy link
Member

@himslm01 I adjusted the position of the clusters selection, feel free to try out the new version: https://github.com/kubenav/kubenav/actions/runs/133598403

@si458 After a first look, it would be a bit more work to move the namespace selection to the menu. I would postpone this to later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants