docs: add missing native encryption at rest support to the limitations

Signed-off-by: Suleyman Akbas <sakbas@redhat.com>

README.md

@@ -52,6 +52,7 @@ end
     * [Single LVMCluster support](#single-lvmcluster-support)
     * [Upgrades from v 4.10 and v4.11](#upgrades-from-v-410-and-v411)
     * [Missing native LVM RAID Configuration support](#missing-native-lvm-raid-configuration-support)
+    * [Missing native encryption at rest support](#missing-native-encryption-at-rest-support)
     * [Snapshotting and Cloning in Multi-Node Topologies](#snapshotting-and-cloning-in-multi-node-topologies)
     * [Validation of `LVMCluster` CRs outside the `openshift-storage` namespace](#validation-of-lvmcluster-crs-outside-the-openshift-storage-namespace)
 - [Troubleshooting](#troubleshooting)
@@ -454,6 +455,10 @@ Simply create a RAID array with `mdadm` and then use this in your `deviceSelecto
 
 _NOTE: Currently, RAID Arrays created with `mdraid` are not automatically recognized when not using any `deviceSelector`, thus they MUST be specified explicitly._
 
+### Missing native encryption at rest support
+
+Currently, LVM Operator does not have a native encryption at rest support. Instead, it is recommended to use encrypted disks if an encryption is desired. [Here](https://www.redhat.com/en/blog/encryption-rest-red-hat-openshift-application-data-edge) is a blog post explaining how to configure encrypted partitions within OpenShift and utilize them as part of LVMCluster.
+
 ### Snapshotting and Cloning in Multi-Node Topologies
 
 In general, since LVMCluster does not ensure data replication, `VolumeSnapshots` and consumption of them is always limited to the original dataSource.

internal/controllers/vgmanager/lvm/lvm_test.go

@@ -583,7 +583,6 @@ func TestNewDefaultHostLVM(t *testing.T) {
 	assert.NotNilf(t, lvm, "lvm should not be nil")
 }
 
-
 func Test_untaggedVGs(t *testing.T) {
 	vgs := []VolumeGroup{
 		{Name: "vg1", Tags: []string{"tag1"}},