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/persistent-storage-csi-gcp-hyperdisk-limitations.adoc
+6-1Lines changed: 6 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,8 @@
7
7
= C3 and N4 instance type limitations
8
8
The GCP PD CSI driver support for the C3 instance type for bare metal and N4 machine series have the following limitations:
9
9
10
+
* You must set the volume size to at least 4Gi when you create hyperdisk-balanced disks. {product-title} does not round up to the minimum size, so you must specify the correct size yourself.
11
+
10
12
* Cloning volumes is not supported when using storage pools.
11
13
12
14
* For cloning or resizing, hyperdisk-balanced disks original volume size must be 6Gi or greater.
@@ -21,5 +23,8 @@ For information about creating the storage class, see Step 2 in Section _Setting
21
23
====
22
24
ifndef::openshift-dedicated[]
23
25
* Clusters with mixed virtual machines (VMs) that use different storage types, for example, N2 and N4, are not supported. This is due to hyperdisks-balanced disks not being usable on most legacy VMs. Similarly, regular persistent disks are not usable on N4/C3 VMs.
26
+
27
+
* A GCP cluster with c3-standard-2, c3-standard-4, n4-standard-2, and n4-standard-4 nodes can erroneously exceed the maximum attachable disk number, which should be 16 (link:https://issues.redhat.com/browse/OCPBUGS-39258[JIRA link]).
* A GCP cluster with c3-standard-2, c3-standard-4, n4-standard-2, and n4-standard-4 nodes can erroneously exceed the maximum attachable disk number, which should be 16 (link:https://issues.redhat.com/browse/OCPBUGS-39258[JIRA link]).
4. If the underlying vSphere environment supports the vSAN file service, then the vSphere Container Storage Interface (CSI) Driver Operator installed by
197
-
{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".
197
+
=======
198
+
ifndef::openshift-dedicated,openshift-rosa[]
199
+
200
+
4. For GCP hyperdisk-balanced disks:
201
+
202
+
* The supported access modes are:
203
+
** `ReadWriteOnce`
204
+
** `ReadWriteMany`
205
+
206
+
* Cloning and snapshotting is disabled for disks with `ReadWriteMany` access mode enabled.
207
+
208
+
* You can attach a single hyperdisk-balanced disk volume in `ReadWriteMany` to a maximum of 8 instances.
209
+
210
+
* You can only resize a disk in `ReadWriteMany` if you detach the disk from all instances.
5. If the underlying vSphere environment supports the vSAN file service, the vSphere Container Storage Interface (CSI) Driver Operator installed by {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