Skip to content

Commit 51a20d3

Browse files
authored
Merge pull request #70639 from danielclowers/CNV-32030
CNV#32030 - Default storage class - planning cluster
2 parents 2c3bc4c + d084a9c commit 51a20d3

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

virt/install/preparing-cluster-for-virt.adoc

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -96,15 +96,15 @@ See xref:../../architecture/architecture-rhcos.adoc#rhcos-about_architecture-rhc
9696

9797
* Supported by {product-title}. See xref:../../scalability_and_performance/optimization/optimizing-storage.adoc#_optimizing-storage[Optimizing storage].
9898

99-
* {rh-storage-first}: You must create a dedicated storage class for Windows virtual machine disks. See link:https://access.redhat.com/articles/6978371[Optimizing ODF PersistentVolumes for Windows VMs] for details.
100-
99+
* You must create a default {VirtProductName} or {product-title} storage class. The purpose of this is to address the unique storage needs of VM workloads and offer optimized performance, reliability, and user experience. If both {VirtProductName} and {product-title} default storage classes exist, the {VirtProductName} class takes precedence when creating VM disks.
100+
+
101101
[NOTE]
102102
====
103-
You must specify a default storage class for the cluster. See xref:../../storage/container_storage_interface/persistent-storage-csi-sc-manage.adoc#persistent-storage-csi-sc-manage[Managing the default storage class]. If the default storage class provisioner supports the `ReadWriteMany` (RWX) xref:../../storage/understanding-persistent-storage.adoc#pv-access-modes_understanding-persistent-storage[access mode], use the RWX mode for the associated persistent volumes for optimal performance.
104-
105-
If the storage provisioner supports snapshots, there must be a xref:../../storage/container_storage_interface/persistent-storage-csi-snapshots.adoc#volume-snapshot-crds[`VolumeSnapshotClass`] object associated with the default storage class.
103+
To mark a storage class as the default for virtualization workloads, set the annotation `storageclass.kubevirt.io/is-default-virt-class` to `"true"`.
106104
====
107105

106+
* If the storage provisioner supports snapshots, you must associate a `VolumeSnapshotClass` object with the default storage class.
107+
108108
include::modules/virt-about-storage-volumes-for-vm-disks.adoc[leveloffset=+3]
109109

110110
[id="live-migration_preparing-cluster-for-virt"]

0 commit comments

Comments
 (0)