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

Namespace filter automatically applied after viewing a deployment #1253

Closed
dlampa opened this issue Sep 13, 2021 · 9 comments
Closed

Namespace filter automatically applied after viewing a deployment #1253

dlampa opened this issue Sep 13, 2021 · 9 comments
Labels
bug Something isn't working

Comments

@dlampa
Copy link

dlampa commented Sep 13, 2021




Describe the bug
A namespace filter corresponding to the namespace of the previously observed deployment is automatically applied to viewing any other resource types.

To Reproduce
Steps to reproduce the behavior:

  1. Have a cluster with multiple namespaces.
  2. Display deployments (:deploy)
  3. Display the details of a specific deployment (describe) by pressing d (haven't checked other ops)
  4. Press ESC, and change resource type, e.g. pods (:pods)
  5. Notice that namespace filter has been set automatically to the namespace of the deployment

This appears to happen only with deployments and not other resources, such as services.

Expected behavior
Do not change the namespace filter on resource change.

Versions (please complete the following information):

  • OS: Linux (Ubuntu 20.04.3)
  • K9s: 0.24.15
  • K8s: 1.20.9-gke

Additional context
Bug was not there in 0.24.14

@derailed
Copy link
Owner

@dlampa Thank you for this issue! Hum... Can't seem to repro?? Followed these steps using 0.24.15 view deployments in all namespaces, describe a deployment then switch to pods and pods display in all namespaces as expected...

@derailed derailed added the question Further information is requested label Sep 16, 2021
@dlampa
Copy link
Author

dlampa commented Sep 16, 2021

@derailed Thanks for the feedback! I just realized I missed one thing for step 3. You have to press Enter to view the containers in the deployment, then press d to describe one of them. Thereafter continue with step 4.

@IvanBodnya
Copy link

@derailed Probably, this can also be closed?
I'm just going through a list of open issues to see where I can contribute ;)

@derailed derailed added bug Something isn't working and removed question Further information is requested labels Nov 23, 2021
@derailed
Copy link
Owner

@IvanBodnya Thank you for looking thru those. I think this issue is still present. Will need a fix...

@IvanBodnya
Copy link

@derailed You're very quick in fixing issues ;)

@derailed
Copy link
Owner

Thank you @IvanBodnya!! LOL Is this a good or bad thing?

@IvanBodnya
Copy link

@derailed I think it's good ;) K9s is evolving! It's an awesome tool! The only downside is that you also have to be quick in solving issues in order to contribute to project ;)

@derailed
Copy link
Owner

@IvanBodnya Indeed! Thank you for landing a hand!!
Just put a comment on the issue if you want to tackle it and I will keep out. Trying to get back to some level of stability after v0.25.X so pedal to the metal unfortunately ;(

@IvanBodnya
Copy link

@derailed I see.. Sure. I really enjoy using this tool. So, decided to make some input into development ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants