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

Latest opened namespace not being saved between k9s sessions #2152

Closed
ghost opened this issue Jun 21, 2023 · 7 comments
Closed

Latest opened namespace not being saved between k9s sessions #2152

ghost opened this issue Jun 21, 2023 · 7 comments

Comments

@ghost
Copy link

ghost commented Jun 21, 2023




Describe the bug

When I used k9s I remember some months ago to be able to select a namespace and explore its pods, then after closing k9s and reopening the shell would reopen on the same screen (list of pods of latest namespace selected) I was before.

To Reproduce
Steps to reproduce the behavior:

  1. Open K9S
  2. Type ":ns"
  3. Select a namespace, see the pods
  4. CTRL + C
  5. Type "k9s"
  6. Now I see all pods of all namespaces of latest connected cluster

Expected behavior
I expect not to see all pods in cluster but to see only the pods inside the latest visited namespace...

Screenshots

Versions (please complete the following information):

  • OS: MacOS Ventura 13.4
  • K9s: 0.27.2
  • K8s: none
@ghost
Copy link
Author

ghost commented Jun 21, 2023

Seems fixed on version 0.27.4

@ghost ghost closed this as completed Jun 21, 2023
@tc-hsteffen
Copy link

Could it be, that this bug has returned?
After updating to the latest version v0.32.4 I have exact the situation described above on Debian GNU/Linux 11 (bullseye)

@chillje
Copy link

chillje commented Apr 26, 2024

Could it be, that this bug has returned? After updating to the latest version v0.32.4 I have exact the situation described above on Debian GNU/Linux 11 (bullseye)

+1

@VladA53
Copy link

VladA53 commented May 27, 2024

Bug returned for 0.32.3 and 0.32.4

@SSvilen
Copy link

SSvilen commented Jun 19, 2024

@derailed can we please reopen this issue?

@bahrb
Copy link

bahrb commented Oct 15, 2024

There is at least a workaround available:

  1. execute k9s info to determine where cluster specific config is located
  2. edit that config.yaml for the certain cluster and add the preferred namespaces to the favorites according to https://k9scli.io/topics/config/
  3. on next k9s startup, namespace favorites will be available

@tc-hsteffen
Copy link

Thank you @bahrb , the workaround works fine!

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants