diff --git a/modules/deploying-lvms-on-sno-cluster.adoc b/modules/deploying-lvms-on-sno-cluster.adoc index e7a11882c6d7..2295a2d4342b 100644 --- a/modules/deploying-lvms-on-sno-cluster.adoc +++ b/modules/deploying-lvms-on-sno-cluster.adoc @@ -30,11 +30,6 @@ Before you begin deploying {lvms} on {sno} clusters, ensure that the following r * You have installed {rh-rhacm-first} on an {product-title} cluster. * Every managed {sno} cluster has dedicated disks that are used to provision storage. -Before you deploy {lvms} on {sno} clusters, be aware of the following limitations: - -* You can only create a single instance of the `LVMCluster` custom resource (CR) on an {product-title} cluster. -* When a device becomes part of the `LVMCluster` CR, it cannot be removed. - [id="lvms-deployment-limitations-for-sno-ran_{context}"] == Limitations diff --git a/modules/lvms-creating-logical-volume-manager-cluster.adoc b/modules/lvms-creating-logical-volume-manager-cluster.adoc index e86443f145ba..acf7daa60b6a 100644 --- a/modules/lvms-creating-logical-volume-manager-cluster.adoc +++ b/modules/lvms-creating-logical-volume-manager-cluster.adoc @@ -35,7 +35,12 @@ You also can perform the same task by using the {product-title} web console. .Procedure . Create the `LVMCluster` custom resource (CR). - ++ +[IMPORTANT] +===== +You can only create a single instance of the `LVMCluster` custom resource (CR) on an {product-title} cluster. +===== ++ .. Save the following YAML in the `lvmcluster.yaml` file: + [source,yaml] @@ -66,6 +71,7 @@ spec: - test1 ---- <1> To create multiple device storage classes in the cluster, create a YAML array under `deviceClasses` for each required storage class. +If you add or remove a `deviceClass`, then the update reflects in the cluster only after deleting and recreating the `TopoLVM-Node` pod. Configure the local device paths of the disks as an array of values in the `deviceSelector` field. When configuring multiple device classes, you must specify the device path for each device. <2> Mandatory: The `LVMCluster` resource must contain a single default storage class. Set `default: false` for secondary device storage classes.