[Feature Request] Quick Search / Filtering

[beasteers]

As an alternative to kubernetes dashboard, Headlamp looks promising.

The features that I think are missing are:

• search across all resources (like the k8s dashboard) - a big search bar in the app header possibly with a filter interface (or filter language)
• Be able to click on the "FAILED" part of the donut chart and show the failed resources (!!!)
  • this is the missing feature that made me start looking for alts in the first place
  • this could even be implemented as a link to a search filter (e.g. type:pod status:Error)
• swipe left to go back (like in the browser)

This is more of a wish, but it would also be great if there was a way to hijack a container in a crashloop and open a shell. This usually doesn't work so you have to redeploy with sleep infinity as an entrypoint/command if you want to be able to SSH into the container. I saw both the exec and attach actions and it got me hopeful about that feature.

[illume]

Hi.

thank you for the suggestions.

Yes the search feature is a good idea. Thanks for bringing it up. We had a plan to introduce a command pallet style search I think. But we first want to finish off the aggregated cluster support. We will come back to you on this, I want to check with the designs and see when/if it will be scheduled to be done.

There was a discussion in another pr about search filter syntax like you mention. It would be pretty nice to work over all the resources like that.

Regarding the swipe back… I hadn’t noticed that wasn’t working in the app version of headlamp. Will have to look into it.

The crash loop feature sounds useful. So, I guess you’d need to copy the config and add that sleep in as you mention. Or maybe there’s some other way to do it. Hrmm.

cheers!

[k8s-triage-robot]

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

[kdeyko]

/remove-lifecycle stale