Open PeteE opened 4 years ago
@PeteE Thank you for this issue! In the mean time, if you don't want to see completed cronjobs you can set successfulJobsHistoryLimit=0 in your cronjob spec. Default is set to 3.
Would persisting filters and sorting into views be a nice generic solution for this? I type /Running
and shift-c
all the time.
I upvote this, setting successfulJobsHistoryLimit=0 is not a solution, I might still need the pods to still be in Kubernetes, I just need the ability from K9S to optional filter out the Completed pods when I am sure they're just noise.
What I do now is sort by state, and invert the sorting, which "works". But sometimes I want to sort by Age, and still hide Completed Pods.
I'm not yet one but having this as Alpha feature could persuade me to a license.
The 2 x shift-s workaround is indeed nice btw :) but when also interacting with regular pods (terminated, etc.) then they "jump" around (obviously).
I figure having them filtered out in the Pods
view makes sense but still leave them accessible when going to CronJob
-> selecting a job -> still seeing them in Jobs
I would also totally like this feature.
A workaround I am using lately is by filtering out completed pods with the search query /!Completed
. By using the k9s HotKeys feature we can put this into hotkeys.yaml
:
hotKeys:
shift-v:
shortCut: Shift-V
description: Filter out completed pods
command: pods /!Completed
keepHistory: true
Now, in the pods list, just press Shift-V and the completed pods are gone.
Is your feature request related to a problem? Please describe. Feature request. We run some
cronjobs
in our cluster which show up asCompleted
pods. These are usually just noise that clutter up thepod
list.For example, we might have a deployment/service named
myapi
and a cronjob likemyapi-cron
. When filtering onmyapi
I'd like to exclude theCompleted
pods.Describe the solution you'd like I'd like a configuration setting that would filter out
Completed
pods from the pod listing.Describe alternatives you've considered A better solution might be a generic filtering mechanism that can be specified in a config file.
Additional context I know this request is fairly vague so I will add some more details once I've given it more though.