Namespace resource overview with quick navigation

[kabakakao]

Problem

When browsing namespaces, there is no direct way to see which resource types contain objects in a particular namespace. Users have to navigate to individual resource views and check each one separately.

Proposal

Add an action to the namespace overview that opens an overlay showing the resource types present in the selected namespace, along with their object counts.

Selecting a resource type would open its existing resource view, scoped to that namespace.

Example

┌─ Resources in namespace: production ──────┐
│ Resource type Count │
│ > Pods 12 │
│ Deployments 4 │
│ Services 6 │
│ ConfigMaps 8 │
│ Secrets 5 │
│ PersistentVolumeClaims 2 │
└─────────────────────────┘

The counts above are illustrative.

Suggested Behavior

Open the overlay for the currently selected namespace.
List namespaced resource types with at least one object.
Support filtering the list by resource type.
Allow selection using the keyboard or mouse.
Open the corresponding resource view in the selected namespace.
Close the overlay with Esc without changing the current view.
Include namespaced custom resources where supported.
Distinguish loading states and missing permissions from genuinely empty results.
Scope and Performance
This would reuse the existing resource views rather than introduce a separate object browser. Cluster-scoped resources would be excluded.

Discovering populated resource types and their counts may require multiple API requests. The implementation should avoid blocking the UI, limit concurrent requests, and show partial results while loading. Missing permissions should not prevent accessible resources from appearing.

[nklmilojevic]

Thanks for the detailed write-up - the scope and performance notes are spot on!

Agreed, there's no good way to answer "what's in this namespace" today. :workloads covers a fixed set of kinds and :xray follows owner references, neither does this.

A few changes to the shape:

1. A view, not an overlay - :ns-resources [ns], plus a key on the namespace row. A view gets filter, sort, view history, esc back and mouse for free, an overlay would need all of that rebuilt. Enter on a kind opens its existing view scoped to that namespace, and esc comes back.
2. enter on a namespace keeps opening pods - this gets its own key.
3. Counts are a snapshot, not live - watching 100+ kinds per namespace is too much. One limit=1 list per kind, count from remainingItemCount, bounded concurrency, rows fill in as they arrive, and r refreshes.
4. Empty kinds are hidden, forbidden kinds stay as rows marked "no access" - so missing permissions don't look like an empty namespace.
5. Cluster-scoped kinds are out, custom resources are in.

I'll create an issue for this and link it here.

[nklmilojevic]

Created #896 for this. Closing this one, follow along there :)