Skip to main content
A PVC remains in Pending when the storage class or access mode does not match a CoreWeave-supported configuration, or when the cluster cannot provision the volume. Quick diagnostic. Run kubectl describe pvc [PVC-NAME] -n [NAMESPACE] and read the Events section for the specific reason. Common causes:
  • Wrong storage class or access mode. Distributed File Storage uses shared-vast with ReadWriteMany. Dedicated VAST uses vast-dedicated with ReadWriteOnce. List the available classes with kubectl get storageclass.
  • PVC in the wrong namespace. PVCs are namespace-scoped. Check that the PVC and the consuming Pod are in the same namespace.
  • Quota exceeded. If total provisioned Distributed File Storage capacity would exceed your cluster’s quota, creation fails. Check the PVC events for quota errors.
For PVC manifests and the full creation procedure, see Create Distributed File Storage volumes or Get started with Dedicated VAST. Contact support if events show errors not listed above.
Server Errors Administrator
Last modified on June 18, 2026