> For the complete documentation index, see [llms.txt](https://docs.one-click.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.one-click.dev/platform/volumes.md).
# Volumes
For persistent storage, you can define volumes. The volumes are the persistent storage for your application. You can define as many volumes as you want. To create a new volume you can click the **New Volume** button.
new volume
You can define the following options:
* name: the name of the volume, must be unique in the **deployment**
* mount path: the mount path of the volume (e.g. /data, /var/lib/mysql)
* size: the size of the volume in **GiB** (gibibyte)
* storage class: the storage class of the volume (the dropdown will show you the available storage classes inside the Kubernetes cluster)
volume overview
{% hint style="info" %}
You cannot change the size or storage class of a volume after creation. If you need to change the size or storage class you need to create a new volume and migrate the data.
{% endhint %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.one-click.dev/platform/volumes.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
