-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Comments
@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 Thanks for the feedback! I just realized I missed one thing for step 3. You have to press |
@derailed Probably, this can also be closed? |
@IvanBodnya Thank you for looking thru those. I think this issue is still present. Will need a fix... |
@derailed You're very quick in fixing issues ;) |
Thank you @IvanBodnya!! LOL Is this a good or bad thing? |
@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 ;) |
@IvanBodnya Indeed! Thank you for landing a hand!! |
@derailed I see.. Sure. I really enjoy using this tool. So, decided to make some input into development ;) |
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:
:deploy
)d
(haven't checked other ops):pods
)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):
Additional context
Bug was not there in 0.24.14
The text was updated successfully, but these errors were encountered: