Inspect a Kubernetes resource

The resource inspector shows one Kubernetes object in detail. Open it by double-clicking a row in a get result, or by clicking the arrow next to the object’s name. It has four tabs: Overview, Events, Logs (Pods only) and JSON. Everything in it is read-only.

The inspector is tied to the exact object you opened, identified by context, namespace, resource type, name and UID. Editing the query or selecting something else in the Explorer does not change what it shows.

The resource inspector for a Pod on the Overview tab: name, namespace and status, two labels, and a containers table with an application container and a completed init container.

Overview

The Overview tab lists:

Name, Namespace, UID and Created (UTC).
Where they apply: Phase, Node, Pod IP and Service type.
Labels, shown as key=value.
For Pods, a Containers table with Name, Type (Application, Init or Ephemeral), State, Ready and Restarts. Hover a container name to see its image.

Click a container name to jump to its logs. See Read Pod logs.

JSON

The JSON tab shows the object definition as the API server returns it, with managedFields removed so the useful parts are easier to read. Copy JSON puts it on the clipboard. Definitions larger than 2 MiB are not displayed.

Events

The Events tab lists events whose involvedObject.uid matches this object. See View events for a Kubernetes resource.

Refresh

The footer button follows the tab you are on: Refresh details, Refresh events or Refresh logs. Click Done to close.

If the object was deleted or replaced by a new one with the same name, the inspector says so:

“This resource is no longer available. Refresh the resource list.”
“This resource was replaced. Close the inspector and refresh the resource list.”

Re-run the get query and open the new row. DevOpsPad checks the UID so it never shows a newer object under an old row.

Supported types

Pods, Deployments, StatefulSets, DaemonSets, Services, ConfigMaps, events, nodes and namespaces. Nodes and namespaces are cluster-scoped; every other type needs a specific namespace.

Permissions

Opening the inspector needs get on the resource type. Events need list on events, and logs need get on pods and pods/log. A permission error stays inside the tab that needs it, so a missing events permission does not hide the Overview. See Kubernetes permissions DevOpsPad needs.