Description
Describe the bug
I always start k9s by passing a --context flag to target a specific kubeconfig context (e.g. k9s --context some-cluster). Occasionally when I start k9s this way, the first screen that loads is a list of my available contexts, instead of a list of pods or the last known thing I was viewing in that context. This seems redundant for obvious reasons. I can't seem to reliably determine why this shows up or what triggers this, and it isn't necessarily always reliable to reproduce this either.
To Reproduce 5210
- Start k9s py bassing a kubeconfig context (
k9s --context some-cluster).
Expected behavior
Expected k9s to start with a pod or other view specific to the context, instead of a list of available contexts.
Additional context
I can confirm that it's a valid context, since I can run kubectl commands against it. Also if I did pass an invalid context in, I would get a "Plugins not loaded" message.
I mainly am curious to know why and how this behavior gets triggered.
I am running 0.50.6 on MacOS 15.2 and installed k9s via brew.