Respect/show namespace set in current KUBECONFIG context

[maboehm]

A context in the kubeconfig can have a namespace set. I am not 100% what the best way is, but maybe:
The namespace switcher could highlight which NS is currently selected.
It could also always put this namespace at the top.
Optionally, there could be a dedicated namespace switcher shortcut for it.

k9s also opens in that namespace by default, but I am not sure if that is the best option either.

[nklmilojevic]

Thanks for the suggestion. I agree with a small first change: show current beside the active namespace, show context default beside the kubeconfig namespace, and open the switcher with the cursor on the active namespace. Both labels can appear on the same row.

Sofka already uses the kubeconfig namespace as a startup fallback. CLI flags, the last namespace saved for the context, and the Sofka default_namespace setting take priority, in that order. We will keep that behaviour, the current list order, and the favourite shortcuts. No new shortcut is needed for this change.

This scope is approved and tracked in #536: #536. I will start implementation in a separate worktree.

[maboehm]

Thank you for quickly adding this.

In my case having a quick way to get to the "current context" namespace would still be great though. I often use tooling that writes my kubeconfig (including the context namespace) (gardenctl to be specific). In that case I might still be talking to the same cluster, but do not want to go back to the last namespace that sofka remember. I understand that this a reasonable default behavior, so an (optional) shortcut (maybe even just in the namespace picker) would be awesome for.

Also, kudos to how quickly you respond to feedback and suggestions - highly appreciated!