Resource Details

The fields, actions, and capacity gauges the Details panel shows for each Kubernetes resource kind in Operator mode, and what it does not show.

Selecting a resource on the Operator canvas opens the Details panel. It shows the resource as Meshery last recorded it from the cluster, and it carries the actions that apply to that kind. Fields with no value are omitted, so each kind shows only what applies.

Node Details

Details panel for a Kubernetes node

Example: Kubernetes Node details.

Container Details

Details panel for a container in a pod

Example: Kubernetes Pod Container details.

  • Opens on a single click. Selecting several resources does not change this: the panel always shows the last resource you clicked.
  • Not live. The panel shows the canvas snapshot immediately, then fetches the resource’s full record once. It does not update while open. Close and reselect the resource to refresh it. See Operator for how the snapshot is built.
  • Two views. Summary (the default) shows the key fields. Details adds the collapsible sections and tables, each titled with its item count, for example Labels (4).
  • Status chip. Shows the resource’s phase when it has one (Running, Pending, Failed, Succeeded, Active, Terminating, Bound, Available, and so on). Otherwise it shows Ready whenever the resource has a Ready condition, whatever that condition’s value. Do not read Ready as a health check.
  • Load failures. While loading you see a loader. If the fetch fails the panel shows Error loading instance details.
KindFields shown
All kindsAge (hours below 24 hours, otherwise days), kind, API version, labels, annotations, condition type names (not their True or False values), and deep links
NodeKubelet version, three capacity gauges, and Capacity and Allocatable tables
PodPod IP, host IP, QoS class, node selector, priority, container count, total restarts, init containers, containers, volumes by type, tolerations
ContainerStatus, ports, start time, image pull policy, restarts, image, container id, environment variables, volume mounts (read-only or read-write), command, arguments, liveness, readiness, and startup probes, resource requests and limits
Deployment, ReplicaSet, StatefulSetAvailable and total pods, ready and total replicas, selector, container images from the pod template, update strategy (StatefulSet)
DaemonSetSelector, images, update strategy. Replica counts may be blank.
ServiceService type, cluster IP, external IP, selector, load balancer ingress addresses, the remaining spec as an expandable tree
IngressRule hosts, the rules as an expandable tree, load balancer addresses
PersistentVolumeCapacity, claim, claim namespace, access modes, storage class
PersistentVolumeClaimRequested size, storage class, access modes
NamespacePhase and finalizers
Secret, ConfigMapSecret type. Secret values are not rendered.
Event and all other kindsThe fields under All kinds only

Container environment variables show their plain values. Values drawn from another source appear as source(apiVersion: fieldPath).

Labels render as key=value chips in the Details view. Selecting a chip toggles that label in the open view’s labels filter and the chip turns green. The filter matches resources carrying any selected label, and the view autosaves. Annotations are listed without actions.

A resource that references a Node, Namespace, or ServiceAccount shows a link for each. Selecting one replaces the view’s kinds filter with that kind and sets the name search to the value, keeping other filters. Use it to walk from a failing pod to the node it landed on.

For a Node, three gauges show how much of the node’s capacity Kubernetes holds back from Pods.

Gauge titleResource
System Reserved CpuCPU
Memory UsageMemory
Disk UsageEphemeral storage

Each value is (capacity - allocatable) / capacity as a percentage, rounded to two decimals, using the node’s reported capacity and allocatable. The gauge color follows the value:

ValueColor
0 to 30 percentTeal-green
Over 30 to 60 percentAmber
Over 60 to 90 percentOrange
Over 90 percentRed

The panel header carries these actions. The same actions are in the canvas right-click menu, except Open Source Design and Download.

ActionOffered onResult
Initiate Terminal SessionPod, ContainerOpens shells. See Open an Interactive Terminal.
Initiate Log SessionPod, ContainerStreams logs. See Stream Container Logs.
Initiate Performance TestService, IngressOpens the load test form. See Run a Performance Test.
Open In DesignResources deployed from a designOpens the source design in Designer with this component focused.
Open Source DesignResources deployed from a designOpens the source design.
DownloadAll kindsSaves the resource record as indented JSON. The file name is the resource name with no .json extension.

A resource counts as deployed from a design when it carries the design identity label that Meshery adds at deploy time. Resources created outside Meshery have no such label and do not offer the design actions. The header also shows Expand and Collapse buttons for every kind; they currently render without an icon.

Kubernetes Event objects appear on the canvas when you enable Events under Monitoring in the Layers panel. It is a plain kind toggle, grouped with the autoscalers. Selecting an event shows the generic fields only. Because events are short-lived and numerous, filter to a namespace first.

The panel does not render Secret values. The stored values still reach your browser: Meshery keeps the Secret and ConfigMap data MeshSync discovers and returns it with the resource, and Download writes it to the JSON file. Treat downloaded files as sensitive, and restrict who can use Operator mode against clusters whose Secrets matter.

Related Reading