Skip to content

Commit f26337f

Browse files
Add that pv's access modes are not constraints on the volume.
1 parent 3470795 commit f26337f

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

content/en/docs/concepts/storage/persistent-volumes.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -477,6 +477,15 @@ In the CLI, the access modes are abbreviated to:
477477
* RWX - ReadWriteMany
478478
* RWOP - ReadWriteOncePod
479479

480+
{{< note >}}
481+
Kubernetes uses volume access modes to match PersistentVolumeClaims and PersistentVolumes.
482+
In some cases, the volume access modes also constrain where the PersistentVolume can be mounted.
483+
Volume access modes do **not** enforce write protection once the storage has been mounted.
484+
Even if the access modes are specified as ReadWriteOnce, ReadOnlyMany, or ReadWriteMany, they don't set any constraints on the volume.
485+
For example, even if a PersistentVolume is created as ReadOnlyMany, it is no guarantee that it will be read-only.
486+
If the access modes are specified as ReadWriteOncePod, the volume is constrained and can be mounted on only a single Pod.
487+
{{< /note >}}
488+
480489
> __Important!__ A volume can only be mounted using one access mode at a time, even if it supports many. For example, a GCEPersistentDisk can be mounted as ReadWriteOnce by a single node or ReadOnlyMany by many nodes, but not at the same time.
481490

482491

0 commit comments

Comments
 (0)