Daily operations

Source: src/routes/cluster/ClusterWorkspace.tsx, src/components/ResourceDetailDrawer.tsx, src-tauri/src/k8s/actions.rs, src-tauri/src/k8s/portforward.rs at v0.18.0.

Read cluster state

Open a cluster from Fleet. Use Workloads for controllers and Pods, Nodes for capacity and conditions, Metrics Explorer for metrics.k8s.io CPU and memory snapshots, requests, limits, allocatable capacity, filters, and local recommendations, and Cloud Map for topology. Select a row to open its detail drawer. Resource lists and details are read-only until you choose an action. Missing metrics-server data or permission is shown as unavailable.

The triage group contains incidents, alert inbox, workloads, pods, events, timeline, and logs. change history is a separate sidebar entry. Treat a suggested relationship as evidence to inspect, not proof of a root cause.

Run an action

Actions appear only where Lumen implements them. App protection and read-only mode can hide or block actions; the API server makes the authoritative RBAC decision when a request runs. Examples include scaling or restarting a workload, deleting a resource, opening a shell, starting a port forward, and attaching a debug container.

1. Confirm the active cluster and namespace in the pane header.
2. Open the target resource and select the action by its visible label.
3. Review any confirmation or protected-context warning.
4. Execute, then verify the resulting resource state rather than assuming the request completed successfully.

Protected contexts can block mutating actions. Kubernetes RBAC remains authoritative even when an action is visible. Debug-container attachment validates Pod identity; ordinary shell and port-forward sessions do not provide that same UID guarantee and can end or change meaning when a Pod is replaced.

See Debug with an ephemeral container, Search and follow logs, and Build an incident handoff.