Persistent storage

From storage to application claims

Storage pages separate cluster-wide PersistentVolumes (PVs), namespace-scoped PersistentVolumeClaims (PVCs) and StorageClass definitions. Inspect capacity, status, access modes and binding details to understand an application’s storage request.

• View PV/PVC details, YAML and binding information.
• Filter PVCs by namespace and resource name.
• Inspect the provisioner and storage policy through StorageClass.
• Use YAML editing and deletion tools where the resource and your permissions allow them.

Investigate a Pending PVC

1. Find the PVC in the application namespace and check its requested capacity.
2. Verify that the selected StorageClass exists and uses the expected provisioner.
3. Inspect PV binding state and Kubernetes events.
4. After the fix, verify that the PVC is Bound and the Pod is running.

Data lifecycle

The effect of deleting a storage resource depends on its reclaim policy, CSI/provisioner and underlying storage system. Resource deletion is not a backup method.

Battani provides a management interface for storage resources. This view does not promise automatic disk backups or snapshot support for every CSI system.