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.

Sign up for GitHub

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

Jump to bottom

Recent namespaces are lost when changing context #2536

Closed
igoooor opened this issue Feb 14, 2024 · 4 comments
Closed

Recent namespaces are lost when changing context #2536

igoooor opened this issue Feb 14, 2024 · 4 comments
Labels
bug Something isn't working InProgress Marks an issue has being worked on

Comments

@igoooor
Copy link

igoooor commented Feb 14, 2024




Describe the bug
If I visit some namespaces in context A, they will appear in the top with [number] shortcuts.
If I then switch to context B (using :ctx) and come back to context A right after, recent namespaces in the top is empty again except for all and default

To Reproduce
See bug description

Expected behavior
After switching back and forth context, I would expect the namespaces to remain. This used to work on previous version (at least on v0.27 as far as I remember)

Versions (please complete the following information):

  • OS: macOS 13
  • K9s: v0.31.8
  • K8s: v1.25.15
@derailed derailed added bug Something isn't working InProgress Marks an issue has being worked on labels Feb 15, 2024
@derailed
Copy link
Owner

@igoooor Nice catch! Thank you! will fix in the next drop

derailed added a commit that referenced this issue Feb 16, 2024
@derailed
[Bug] fix #2536
2f76223
@derailed derailed mentioned this issue Feb 16, 2024
Merged
@thedlund
Copy link

I just upgraded from version 0.27.4 -> 0.31.9 and I can reproduce this issue.

@den-is
Copy link
Contributor

den-is commented Feb 26, 2024 •
edited
Loading

Still happens with 0.31.9.
Without switching context, just exiting/opening the app again looses visited namespaces.
using custom location for k9s configs, configured with $K9S_CONFIG_DIR
removing k9s directory for cluster config and starting from scratch doesn't help

placintaalexandru pushed a commit to placintaalexandru/k9s that referenced this issue Apr 3, 2024
@derailed
K9s/release v0.31.9 (derailed#2543)
8064419 
* [Bug] fix derailed#2535

* [Bug] fix derailed#2532

* [Bug] fix derailed#2536

* [Bug] fix derailed#2533

* [Bug] fix derailed#2538

* [Maint] cleaning up

* Release notes
@SaeidAshian
Copy link

This is related to this bug which seems to be fixed but I can see it is remaining. I can reproduce it on v0.32.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working InProgress Marks an issue has being worked on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@derailed @igoooor @thedlund @den-is @SaeidAshian