That's basically why the input field works as a filter, so that user don't have to scroll forever to find the namespace. It is also the default size defined by the material design. We really don't like to override their defaults if this isn't absolutely necessary.

I do not disagree with you,
but it is just annoying to me having to leave my mouse just go to the keyboard to type the namespace I want and then switch back to my mouse.

The material design "defaults" are broken in my view if they result in something this badly formatted.

The height of the alarm panel isn't anywhere near that short - why is the namespace list so short - and why so much excessive padding around every line.

.mat-select-panel {
   max-height: 600px;
}

by itself is a huge improvement in usability. Absent a code change - is there any good/easy way to add custom CSS during deployment?

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

/lifecycle frozen

/assign

/assign