Number shortcuts to namespaces

[rettelbachj]

First of all: thanks for your great work. :) In k9s I really use the feature a lot where I can type a number and switch between namespaces. I.e.:

Here I can type 0 to see resources in all namespaces and to see resources in the namespace default

The list of namespaces in k9s is generated by the history of how many times a namespace was consulted. What do you think of this feature? Did I make clear what it should do?

[bachgarash]

I came to suggest this as well. It was really useful in k9s.

Also, by default Sofka opens all namespaces which is not ideal imho. I work with fairly large cluster(s) and it fetches all pods. I'd suggest to fetch default namespace pods by default instead.

[nklmilojevic]

Thanks for the kind words, and for the screenshot - it made the ask clear :)

sofka is inspired by k9s but it's a separate product, so matching it isn't a goal on its own. In this case most of it is already there:

1. Number keys - already in. 0 selects all namespaces and 1 to 9 select your favourite namespaces, both in the resource table and inside the n switcher while its filter is empty. Set them with favorite_namespaces in the config (see configuration). The header shows them next to the current namespace, and the k9s import brings locked k9s favourites over too.
2. Filling the list from history - no. Keys that reassign themselves based on what you visited break muscle memory - 3 should be the same namespace tomorrow. Recently used namespaces already show up in the n switcher (marked ·) right below the favourites, so history is one keypress away without moving the numbers around.
3. @bachgarash on starting in all namespaces - sofka doesn't default to all namespaces. On startup it uses the namespace you last picked on that context, then default_namespace from the config, then the kubeconfig namespace (usually default). If you see all namespaces, it's because that was the last choice on that context. Pick a namespace once and sofka remembers it, or set prefer_context_namespace = true if you want the kubeconfig namespace to win over history.

Nothing to build here, so I'm closing this one.

[rettelbachj]

Thanks a lot for your explanations! The favorite namespaces feature might do the trick!
Only wanted to reply to number 2:
You're totally right. Actually IDK how k9s does it exactly. It just feels seemless :)