> For the complete documentation index, see [llms.txt](https://ai-docs.fptcloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-docs.fptcloud.com/fpt-gpu-cloud/gpu-cluster/managed-k8s-with-gpu-virtual-machine/tutorial/persistent-storage.md).
# Persistent Storage
FPTCloud's Managed FKE product provides a block storage (CSI – Container Storage Interface) solution, supporting users to store, read, and write data at desired speeds using . Managed FKE clusters provide a default storage class using policy disks similar to **worker pool worker group-based** policy disks. FPTCloud's CSI supports online volume resizing.
Users can create PVCs (persistent volume claims) using these storage classes and build applications that utilize these PVCs.
If users wish to create a new storage class with a different policy disk type, proceed as follows:
* Save the default storage class configuration.
* Modify the policy disk.
* Rename the storage class.
* Remove the annotation for the default storage class.
*Do not modify the cluster's default storage class configuration. If a user changes this setting, it will automatically roll back to the default configuration. To use a new storage class, you must specify the \`storageClassName\` in the PersistentVolumeClaim configuration.*
---
# 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://ai-docs.fptcloud.com/fpt-gpu-cloud/gpu-cluster/managed-k8s-with-gpu-virtual-machine/tutorial/persistent-storage.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.
