# Volumes

In Kubernetes, a volume is an abstraction of a file system that is available to applications. In Portainer you can manage the volumes that have been deployed by your applications within your cluster.

{% hint style="info" %}
Volumes can also be added [using a manifest](/user/kubernetes/applications/manifest.md) by clicking **Create from manifest**.
{% endhint %}

{% content-ref url="/pages/-Mi-N4gt6ws8W5tqWrUe" %}
[Inspect a volume](/user/kubernetes/volumes/inspect.md)
{% endcontent-ref %}

{% content-ref url="/pages/-Mhuf39xygebrDMmjnF1" %}
[Remove a volume](/user/docker/volumes/remove.md)
{% endcontent-ref %}

## Volumes tab

Lets you view information about the volumes that exist within the cluster, including:

* The namespace that each volume is a part of.
* Which applications use each volume.
* The storage class each volume belongs to.
* The size of each volume.
* When the volumes were created and by whom.
* A volume with the **external** flag was created outside of Portainer, which means Portainer has limited knowledge on it compared to one created within Portainer. A label of **unused** means that Portainer cannot see any applications that are using this volume. This label may also appear on **external** resources because of the limited information available.

<figure><img src="/files/7VzckvleD2UssT78Wx3C" alt=""><figcaption></figcaption></figure>

## Storage tab

The storage tab lists the storage classes available within your infrastructure along with the disk space used by each volume. Each storage class can be expanded to list the volumes contained within.

<figure><img src="/files/zRjqjuhRAXQ1uuKWtMlZ" 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/user/kubernetes/volumes.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.