Explore your Kubernetes pods, live or historical
Kubernetes gets its own section under Infrastructure: a live map of every pod, a pod table that takes k9s keys, and a side panel that shows why a pod failed.
Kubernetes used to be one resource type among many on the Resources page. It now has its own section under Infrastructure, built around the question you open it with: which pods are unhappy, and why. The pages run live by default, and the same control rewinds them to any past window, so you can ask that question of the cluster as it is now or as it was when it broke.

Start wide, then zoom in
The Map draws every pod in every cluster, grouped by cluster and namespace and colored by health. Click a cluster to zoom into it, a namespace to go further, a pod to open it. Beside the map, Needs attention says what is wrong and how many pods it affects: failed, pending, in an unknown phase, not ready, near the CPU limit, near the memory limit.
The Table trades the overview for detail. Every pod is a row carrying its namespace, its age, its status, how often it has restarted, how much CPU and memory it is using, and how much of its limit that is. Group the rows by cluster, namespace or node, and filter them by name, cluster, namespace, node or IP.

The k9s keys, in the browser
The table takes the keys you already type. j and k move, g and Shift+G jump to the ends, Enter or d opens a pod, y its YAML, l its logs, e its events, o its node, p its parent workload, c copies the name and / filters. Shift+N, Shift+A, Shift+S, Shift+C and Shift+M sort by name, age, status, CPU and memory.
Why that pod failed
Open a pod and the side panel answers it without sending you anywhere else.
- Containers gives each container's current state and, once object collection is on, its last termination, with the reason, exit code and signal.
- Events sits next to the CPU, memory and network charts. Kubernetes records no event when a container is killed, so Dash0 reconstructs those rows from the container's status metrics and marks them as approximate.
- Logs are filtered to the pod, and to one container when you pick one. A container that terminated without writing anything says so, and links to the event that explains it.
- Traces group into operations with p50, p95 and error counts, and open in place.
- Related resources walks the cluster, its nodes and the namespace's pods on them, and the workload down through its ReplicaSets.

The YAML, as it is in the cluster
The YAML tab shows the object's manifest as it was last collected, stamped with when. An object that has since been deleted still shows its last known state.
Manifests reach Dash0 as log records from the OpenTelemetry Collector's k8sobjects receiver, so any collector you already run can send them. The Dash0 operator runs that receiver for you once you turn Kubernetes object collection on for the cluster and for the namespaces you want manifests from. Before anything leaves your cluster, it masks the values of environment variables and removes the annotations that kubectl and similar tools use to store a serialized copy of the whole manifest.

Live, or any moment you choose
The pages follow your cluster as it changes. Pause them when you want to read a row without it moving under you, or pick a past window, such as yesterday or this day last week, and see the cluster as it was then, with a banner saying so and one click back to live.
Workloads, Nodes and Storage are next.