> For the complete documentation index, see [llms.txt](https://docs.tensorwave.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tensorwave.com/kubernetes/nodes.md).

# 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. |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tensorwave.com/kubernetes/nodes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.