# Inspect a node

To view details of an individual node in your cluster, from the menu expand **Cluster** and select **Details**, then scroll down and click on the name of the node you want to inspect.

<figure><img src="/files/XlYpNGcwbV8dK1USdrWC" alt=""><figcaption></figcaption></figure>

Information about the cluster is separated into three screen tabs: **Node**, **Events**, and **YAML**. An **Applications running on this node** section remains at the bottom of the page.

## Node

The **Node** tab summarizes the following information about the selected node:

| Field/Option    | Overview                                                                               |
| --------------- | -------------------------------------------------------------------------------------- |
| Hostname        | The hostname of the node.                                                              |
| Kubernetes API  | The address and port of the Kubernetes API for this node.                              |
| Role            | The role of the node.                                                                  |
| Kubelet version | The version of kubelet on the node.                                                    |
| Creation date   | The date when this node was created.                                                   |
| Status          | The status of the node.                                                                |
| Availability    | Defines the availability of the node. Options are **Active**, **Pause** and **Drain**. |

<figure><img src="/files/IgwM6Y3zJUXJXm7tG9zD" alt=""><figcaption></figcaption></figure>

### Resource reservation

This section provides details about resource reservations assigned on the node as well as the node's resource usage.

{% hint style="info" %}
**Memory used** and **CPU used** are only displayed if you have [enabled using the metrics API](/sts/user/kubernetes/cluster/setup.md#enable-features-using-metrics-server).
{% endhint %}

<figure><img src="/files/Z7AchfmsWO7KsDobMFnW" alt=""><figcaption></figcaption></figure>

### Labels

This section lists the labels that apply to the node. You can add additional labels if required, as well as edit non-system labels.

<figure><img src="/files/nTAgf5zgZ74BLyeZwiTr" alt=""><figcaption></figcaption></figure>

### Taints

In this section you can add taints to prevent certain pods being deployed on the node.

<figure><img src="/files/6iQNRBIPT3HDeWw4rxTD" alt=""><figcaption></figcaption></figure>

## Events

This section shows information about node-related events.

<figure><img src="/files/e6LsggDSfYMi3OFxIF31" alt=""><figcaption></figcaption></figure>

## YAML

{% hint style="info" %}
Editing the YAML in this view is only available in Portainer Business Edition.
{% endhint %}

This section shows the node YAML within an editor. To apply any changes you make within the YAML editor, select the **Apply changes** button, and select **Apply changes** if you are sure. Changes are made by calling the Kubernetes API to patch the relevant resources. Any resource removals or unexpected resource additions that you make in the YAML will be ignored. Note that editing is disabled for resources in namespaces marked as system.

<figure><img src="/files/smaV8uTEubnXVu5DQwnv" alt=""><figcaption></figcaption></figure>

***

## Applications running on this node

This section provides information about the applications running on the selected node. Clicking the application name will take you to the application details page for that application.

<figure><img src="/files/qSHvokTyf9tdaNOBOOg8" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.portainer.io/sts/user/kubernetes/cluster/details/node.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.