kube context in running k9s is no longer sticky, during kubectx context switch

[pgier]

Describe the bug
If I start a k9s session, then change the current kube context using CLI commands in a separate terminal, then the context in the k9s session also changes. Previously I was able to start one k9s, change context, then start another k9s so that I can have two k9s sessions running in parallel pointing to two different clusters.

After a recent update, all k9s windows automatically switch to the current context in my kube config.

To Reproduce
Steps to reproduce the behavior:

1. Start k9s
2. Change current kube context using kubectx or another tool
3. See that k9s shortly updates the Context and Cluster fields, but pods are still from the original cluster.

Expected behavior
This seems to be a recent change because previously my k9s windows were sticky to whatever cluster they started on.

Versions (please complete the following information):

• OS: Mac
• K9s: 0.39.1
• K8s: 1.26

[pgier]

Originally, I thought k9s actually changed the cluster that it's pointing to, but this seems to only affect the header fields. K9s still gets resources from the original cluster with which it was started, but the header fields now point to a different cluster.

[derailed]

@pgier Thank you for the heads up Paul!
Indeed! I ran into this as well ;(
I'll have a fix in place for the next drop.

[derailed]

Fixed v0.32.0