-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Description
Describe the bug
Since the feature to have a config file per context has been introduced, having the same context open in multiple kubeconfigs / k9s leads to the namespace getting reset.
I have k9s open and do :ns, select a namespace and press <enter> and k9s switches to the default namespace.
Or I somehow managed to get into a namespace do :ma, or any other resource, and k9s switches to that resource in the default namespace
To Reproduce
Really weird to reproduce, doesn't happen always, but I'm happy to help with debugging
Historical Documents
I've tried to screen record this, but just waiting a bit after it happened a couple of times often "fixes" it.
Expected behavior
Not this
Screenshots
Versions (please complete the following information):
- OS: Arch Linux
- K9s: 0.31.5
- K8s: N/A
Additional context