For the complete documentation index, see llms.txt. This page is also available as Markdown.

Nodes

The Nodes section within the Kubernetes tab gives you a detailed look at every node in your cluster, including its current status, role, Kubernetes version, and hardware resource specifications such as GPU count, CPU cores, and available memory.

To access this view, navigate to your cluster, select the Kubernetes tab, then choose Nodes from the left sidebar.


Summary Cards

Four summary cards at the top of the Nodes view give you a quick breakdown of node states across the cluster:

Card
Description

Ready

The number of nodes in a Ready state and available to schedule workloads.

Not Ready

The number of nodes that are not ready. This may indicate a problem that requires investigation.

Control Plane

The number of nodes serving as control plane nodes, responsible for managing the cluster state.

Workers

The number of worker nodes available to run your workloads.


Node Table

Below the summary cards, a table lists every node in the cluster with the following columns:

Column
Description

Hostname

The node's hostname. Click the copy icon alongside it to copy the hostname to your clipboard.

Status

The current Kubernetes node status. See Node Statuses below for possible values.

Role

Whether the node is a worker or a control plane node.

Version

The Kubernetes version running on the node (e.g. v1.34.7+rke2r1).

GPU

The number of GPUs detected on the node. A - indicates a CPU-only node with no GPU resources.

CPU

The total number of CPU cores on the node.

Memory

The total memory available on the node, displayed in kibibytes (Ki).

More Info

Click the info icon to view additional details for that node.


Node Statuses

The Status column reflects the Kubernetes node condition reported by the control plane:

Status
Description

Ready

The node is healthy and ready to accept workloads.

Not Ready

The node is reachable but is failing one or more health checks. Workloads will not be scheduled to this node.

Unknown

The control plane has lost contact with the node. This typically means the node has gone offline or the kubelet has stopped reporting.

Last updated