Release notes for LVMS

Author: sr1kar99

release_notes/ocp-4-20-release-notes.adoc

@@ -111,6 +111,21 @@ Instead of rebooting nodes after each individual change, you can apply all confi
 
 For more information, see xref:../edge_computing/policygenerator_for_ztp/ztp-configuring-managed-clusters-policygenerator.adoc#ztp-coordinating-reboots-for-config-changes_ztp-configuring-managed-clusters-policygenerator[Coordinating reboots for configuration changes].
 
+[id="ocp-release-edge-computing-networkpolicy-support-for-lvms_{context}"]
+==== NetworkPolicy support for the {lvms} Operator
+
+The {lvms} Operator now applies Kubernetes `NetworkPolicy` objects during installation to restrict network communication to only the required components. This feature enforces default network isolation for {lvms} deployments on {product-title} clusters.
+
+[id="ocp-release-edge-computing-hostname-label-for-pv_{context}"]
+==== Support for hostname labelling for persistent volumes created by using the {lvms} Operator
+
+When you create a persistent volume (PV) by using the {lvms} Operator, the PV now includes the `kubernetes.io/hostname` label. This label shows which node the PV is located on, making it easier to identify the node associated with a workload. This change only applies to newly created PVs. Existing PVs are not modified.
+
+[id="ocp-release-edge-computing-default-namespace_{context}"]
+==== Default namespace for the {lvms} Operator
+
+The default namespace for the {lvms} Operator is now `openshift-lvm-storage`. You can still install {lvms} in a custom namespace.
+
 [id="ocp-release-notes-extensions_{context}"]
 === Extensions ({olmv1})