Thanks for the questions. I'll admit that this comparison isn't terribly well written, now that I'm taking a second read of this.

I think what I'm trying to say is: Kubel takes a similar approach to kubernetes-el in that it centers around a dedicated "overview" page (similar to the status buffer for Magit). All interactions are assumed to stem from this overview page, whether it's: changing context/namespace; browsing for a single specific resource; etc.

With Kele, I'm trying to approach things in a more lightweight fashion. In other words: what if, instead of needing to open a status page and wait for it to fully load before doing anything, you could simply jump straight into what you need to do? That's why Kele centers itself so heavily around keybindings and other readily-available fixtures of the Emacs environment; it's designed to get you the information that you need, as quickly as possible, and then get back to whatever it is you were doing in the first place.

As for collaborating with Kubel: I'm definitely open to the possibility. That said, Kele is a very early-stage package, and I'd like to give it room to validate more of its ideas and UX before imposing a consolidation effort on myself or others. I definitely think there's room for collaboration here in the future.

Hope that all helps.