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

Add ability to filter by pod status and by labels #7547

Open
yasinzaehringer-paradime opened this issue Nov 29, 2022 · 4 comments · May be fixed by #9572
Open

Add ability to filter by pod status and by labels #7547

yasinzaehringer-paradime opened this issue Nov 29, 2022 · 4 comments · May be fixed by #9572
Assignees
@avanish23
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@yasinzaehringer-paradime
Copy link

yasinzaehringer-paradime commented Nov 29, 2022 •
edited
Loading

What would you like to be added?

Add more functionality for filtering (e.g.) pods:

  • by status
  • by labels and annotations
  • etc

Also add functionality not only to select matching rows, but also remove matching rows from result.

The selector should also be part of the URL - so it can be shared.

Why is this needed?

To understand bigger clusters it's important to be able quickly filter. The most common use case I have is this one:

  • we have lot's of cronjobs (and we retain the 3 latest runs) -> lot's of Completed pods
  • we have a few pods -> quite a few Running pods

Atm, our dev cluster reports 724 pods and I am interested in let's say failed pods, how do I get there? Sorting by Status and click through a few pages until I find Status=Error? It's better to be able to write more complex filters.
@yasinzaehringer-paradime yasinzaehringer-paradime added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 29, 2022
@yasinzaehringer-paradime
Copy link
Author

yasinzaehringer-paradime commented Nov 29, 2022 •
edited
Loading

I have this branch (which is a slightly hacky version) of what I have in mind: 84a2ec5 - feedback welcome (and I know that the pre-commit hook fails).

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 27, 2023
@maciaszczykm maciaszczykm added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 6, 2023
@avanish23
Copy link
Contributor

/assign

@avanish23 avanish23 linked a pull request Oct 26, 2024 that will close this issue
Open
@avanish23
Copy link
Contributor

These are too many asks for one issue. I have opened a PR that provides backend support to start filtering the pods with various other parameters.
I think it will be better to track the remaining asks in separate issues; I will probably create them once this PR is merged (might take time).
Tagging @shu-mutou @floreks for suggestions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@avanish23 avanish23

Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: Add ability to filter by resource labels and annotations avanish23/dashboard
5 participants
@maciaszczykm @k8s-ci-robot @k8s-triage-robot @avanish23 @yasinzaehringer-paradime