Prompt
Do I need a shared filesystem for Kubernetes persistent volumes?
Latest observation
Oct 12, 2026
OpenAI APIWeb search: off
No — not necessarily.
A Kubernetes PersistentVolume (PV) is just storage that can outlive a pod. Whether it must be on a shared filesystem depends on how the volume will be used.
Common cases
-
Single-pod / single-node use
- You do not need a shared filesystem.
- Examples:
local,hostPath(for testing), or cloud disks like EBS/GCE PD/Azure Disk. - Usually these are ReadWriteOnce (RWO), meaning one node at a time can mount them.
-
Multiple pods/nodes need the same data at the same time
- Yes, you need a shared filesystem or shared storage system.
- Examples: NFS, CephFS, GlusterFS, AWS EFS, Azure Files, GCP Filestore.
- Typically these support ReadWriteMany (RWX).
Rule of thumb
- If only one pod needs to mount the volume: block storage is fine
- If many pods need simultaneous access: shared filesystem required
Important nuance
Kubernetes itself doesn’t require a shared filesystem; the requirement comes from your application’s access pattern and the access mode supported by the storage backend.
If you want, I can also explain the difference between RWO, RWX, and ROX with examples.