Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to show pod list on startup instead of namespace list #3015

Open
OvervCW opened this issue Dec 6, 2024 · 2 comments
Open

Ability to show pod list on startup instead of namespace list #3015

OvervCW opened this issue Dec 6, 2024 · 2 comments
Labels
question Further information is requested

Comments

@OvervCW
Copy link

OvervCW commented Dec 6, 2024




Is your feature request related to a problem? Please describe.
I generally open k9s to quickly do some work in the namespace that my context is currently set to and in older versions k9s would simply show all of the pods in that namespace when I start it up. However, the latest version (v0.32.7) instead shows a list of namespaces, where I have to select the current one first. This makes k9s a little bit less intuitive to use.

Describe the solution you'd like
Is there a way to tell k9s to open the list of pods rather than the list of namespaces on startup?

Describe alternatives you've considered

Additional context

@derailed derailed added the question Further information is requested label Dec 8, 2024
@derailed
Copy link
Owner

derailed commented Dec 8, 2024

@OvervCW K9s should open up to the last view used in the previous session unless there are issues in your k9s configuration (check debug logs). You can tell k9s to open on any view via k9s -c po. If a namespace is set for your context it should open the last resource viewed in the previous session for that namespace.

@OvervCW
Copy link
Author

OvervCW commented Dec 9, 2024

@derailed Running k9s -c po one time for every context fixed the problem for me! It's now opening the list of pods instead of the list of namespaces every time.

As far as I'm aware I don't have any custom k9s configuration and I tried quitting k9s both with Ctrl-C and :q after opening the pods view, but it's only k9s -c po that seems to be able to permanently make the change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants