Reorganize the clusters tree

I had a meeting with one guy in my team (he is working on the kubernetes plugin in IntelliJ) and we discussed about how to reorganize better the clusters tree to reduce the confusion in it.

It often happens that the clusters tree is filled in with context nodes belonging to the same cluster that only differ for their namespace or user.

An example is the image below

Our idea was to group the nodes based on their host so to have atleast all namespaces together and make the life of a developer that want to switch namespace inside the same cluster easier.

If we take the case above as an example we would end up with 4 nodes instead of 20+.

127-0-0-1:8443
192-168-42-19:8443
192-168-42-72:8443
api-crc-testing:6443

I don’t know if you already tried it and there were some limitations, what do you think? Any other idea?

cc @itowlson @gorkem @squillace @adietish

[lstocchi]

I like this idea as well. It also gives us the freedom (if we decide to do that) to create different selections (all contexts, only namespaces from current cluster, only clusters) so to replicate what happens with kubectx/kubens functionality. Users can then choose which one to use based on their needs or their preferences.

BTW +1

[gorkem]

How about moving the context list and hence context switching out of tree. Basically tree shows the resources for the currently selected context only. For context listing and switching we can do something similar to what git extension does for branches.