You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/storage-persistent-storage-pv.adoc
+51-46Lines changed: 51 additions & 46 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -95,6 +95,19 @@ Direct matches are always attempted first. The volume's modes must match or cont
95
95
96
96
All volumes with the same modes are grouped, and then sorted by size, smallest to largest. The binder gets the group with matching modes and iterates over each, in size order, until one size matches.
97
97
98
+
ifndef::microshift[]
99
+
[IMPORTANT]
100
+
====
101
+
Volume access modes describe volume capabilities. They are not enforced constraints. The storage provider is responsible for runtime errors resulting from invalid use of the resource. Errors in the provider show up at runtime as mount errors.
102
+
103
+
ifndef::openshift-dedicated,openshift-rosa[]
104
+
For example, NFS offers `ReadWriteOnce` access mode. If you want to use the volume's ROX capability, mark the claims as `ReadOnlyMany`.
105
+
106
+
iSCSI and Fibre Channel volumes do not currently have any fencing mechanisms. You must ensure the volumes are only used by one node at a time. In certain situations, such as draining a node, the volumes can be used simultaneously by two nodes. Before draining the node, delete the pods that use the volumes.
107
+
endif::openshift-dedicated,openshift-rosa[]
108
+
====
109
+
endif::microshift[]
110
+
98
111
The following table lists the access modes:
99
112
100
113
.Access modes
@@ -104,6 +117,9 @@ The following table lists the access modes:
104
117
|ReadWriteOnce
105
118
|`RWO`
106
119
|The volume can be mounted as read-write by a single node.
120
+
|ReadWriteOncePod ^[1]^
121
+
|`RWOP`
122
+
|The volume can be mounted as read-write by a single pod on a single node.
Volume access modes are descriptors of volume capabilities. They are not enforced constraints. The storage provider is responsible for runtime errors resulting from invalid use of the resource.
122
-
123
-
ifndef::openshift-dedicated,openshift-rosa[]
124
-
For example, NFS offers `ReadWriteOnce` access mode. You must
125
-
mark the claims as `read-only` if you want to use the volume's
126
-
ROX capability. Errors in the provider show up at runtime as mount errors.
127
-
128
-
iSCSI and Fibre Channel volumes do not currently have any fencing
129
-
mechanisms. You must ensure the volumes are only used by one node at a
130
-
time. In certain situations, such as draining a node, the volumes can be
131
-
used simultaneously by two nodes. Before draining the node, first ensure
|{ibmpowerProductName} Virtual Server Disk | ✅ | ✅ | ✅
163
-
|IBM VPC Disk | ✅ | - | -
164
-
|iSCSI | ✅ | ✅ | -
165
-
|Local volume | ✅ | - | -
166
-
|NFS | ✅ | ✅ | ✅
167
-
|OpenStack Manila | - | - | ✅
168
-
|{rh-storage-first} | ✅ | - | ✅
169
-
|VMware vSphere | ✅ |- | ✅ ^[3]^
162
+
//|GlusterFS | ✅ |✅ | ✅ | ✅
163
+
|HostPath | ✅ |✅ | - | -
164
+
|{ibmpowerProductName} Virtual Server Disk | ✅ |✅ | ✅ | ✅
165
+
|IBM VPC Disk | ✅ |✅ | - | -
166
+
|iSCSI | ✅ | ✅ |✅ | -
167
+
|Local volume | ✅ |✅ | - | -
168
+
|NFS | ✅ | ✅ |✅ | ✅
169
+
|OpenStack Manila | - |✅ | - | ✅
170
+
|{rh-storage-first} | ✅ |✅ | - | ✅
171
+
|VMware vSphere | ✅ |✅ | - | ✅ ^[4]^
170
172
endif::[]
171
-
172
173
|===
173
174
[.small]
174
175
--
175
176
1. ReadWriteOnce (RWO) volumes cannot be mounted on multiple nodes. If a node fails, the system does not allow the attached RWO volume to be mounted on a new node because it is already assigned to the failed node. If you encounter a multi-attach error message as a result, force delete the pod on a shutdown or crashed node to avoid data loss in critical workloads, such as when dynamic persistent volumes are attached.
176
-
2. Use a recreate deployment strategy for pods that rely on Amazon EBS.
177
+
178
+
2. ReadWriteOncePod is a Technology Preview feature.
179
+
180
+
3. Use a recreate deployment strategy for pods that rely on AWS EBS.
181
+
177
182
ifndef::openshift-dedicated,openshift-rosa[]
178
-
3. If the underlying vSphere environment supports the vSAN file service, then the vSphere Container Storage Interface (CSI) Driver Operator installed by
183
+
4. If the underlying vSphere environment supports the vSAN file service, then the vSphere Container Storage Interface (CSI) Driver Operator installed by
179
184
{product-title} supports provisioning of ReadWriteMany (RWX) volumes. If you do not have vSAN file service configured, and you request RWX, the volume fails to get created and an error is logged. For more information, see "Using Container Storage Interface" -> "VMware vSphere CSI Driver Operator".
0 commit comments