Supported resource families
Operational entries
Section titled “Operational entries”The first sidebar block contains triage with incidents, alert inbox, workloads, pods, events, timeline, and logs. Standalone entries are nodes, metrics explorer, namespaces, compare, and device resources.
Resource groups
Section titled “Resource groups”- workloads: deployments, statefulsets, daemonsets, replica sets, replication controllers, jobs, cronjobs, job sets, and pod templates. Pods are available from triage.
- config: configmaps, secrets, resource quotas, limit ranges, HPAs, VPAs, PDBs, priority classes, runtime classes, mutating webhooks, and validating webhooks.
- network: services, endpoints, endpoint slices, ingresses, ingress classes, gateway classes, gateways, HTTP routes, GRPC routes, network policies, and debugger.
- storage: PVCs, persistent volumes, storage classes, CSI drivers, CSI nodes, and volume attributes.
- RBAC: service accounts, roles, role bindings, cluster roles, and cluster role bindings.
- cluster metadata: nodes, namespaces, events, leases, controller revisions, API services, and certificate requests.
The remaining entries are workspaces, change history, access control, helm, custom resources, security, and cloudmap. argocd and tekton are inserted only when their APIs are discovered.
Presence in this list means a read or inspection route exists. It does not imply every kubectl mutation is supported. Secrets are presented through a redacted workflow, cluster-scoped families ignore the namespace picker, optional APIs can be absent, and forbidden families remain unavailable rather than appearing empty. compare is a comparison view rather than a Kubernetes resource family.
Source: src/routes/cluster/ClusterWorkspace.tsx, src/lib/k8s/resourceRegistry.ts, src-tauri/src/k8s/registry.rs at v0.18.0.