Persistent volumes provide storage for stateful apps, databases, and workloads that need data to survive restarts.
- Creates and mounts PersistentVolumeClaims for deployments.
- Lets you switch active volumes and delete volumes when supported.
- Supports automatic storage expansion when usage approaches capacity and the storage class allows expansion.
- Works with snapshots and restores when snapshot support is installed.
- Your app stores uploaded files or persistent data.
- You are running a database or stateful service.
- You need storage that remains after pod restarts.
- A deployment that can mount a volume.
- A valid mount path.
- Available storage class and plan limits.
Screenshot Required
- Open the deployment detail page.
- Open the volume controls.
- Create or attach a volume.
- Enter the size, access mode, storage class, and mount path requested by the UI.
- Save the volume configuration.
- Wait for the deployment to update and become ready.
- Use snapshots if you need backup or restore workflows.
- Using an invalid or conflicting mount path.
- Expecting a single-writer volume to attach to multiple pods at once.
- Deleting a volume before confirming whether it contains needed data.
- Use snapshots before risky application or data changes.
- Plan storage size with growth in mind.
- If pods are pending with multi-attach errors, review the volume access mode and rollout status.