diff --git a/release_notes/ocp-4-13-release-notes.adoc b/release_notes/ocp-4-13-release-notes.adoc
index a68cb9e70ecd..b03e37b73a73 100644
--- a/release_notes/ocp-4-13-release-notes.adoc
+++ b/release_notes/ocp-4-13-release-notes.adoc
@@ -63,8 +63,23 @@ With this release, {product-title} {product-version} introduces a {op-system-bas
 
 * Some device drivers have been deprecated, see the link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/considerations_in_adopting_rhel_9/assembly_hardware-enablement_considerations-in-adopting-rhel-9#unmaintained-hardware-support[{op-system-base} documentation] for more information.
 
+[id="ocp-4-13-ipi-powervs"]
+==== {ibmpowerProductName} Virtual Server using installer-provisioned infrastructure (Technology Preview)
+
+Installer-provisioned Infrastructure (IPI) provides a full-stack installation and setup of {product-title}.
+
+//For more information, see xref :../installing/installing_ibm_powervs/preparing-to-install-on-ibm-power-vs.adoc#preparing-to-install-on-ibm-power-vs[Preparing to install on {ibmpowerProductName} Virtual Server].
+
+[id="ocp-4-13-powervs-csi-driver-operator"]
+==== {ibmpowerProductName} Virtual Server Block CSI Driver Operator (Technology Preview)
+
+{product-title} is capable of provisioning persistent volumes (PVs) by using the Container Storage Interface (CSI) driver for {ibmpowerProductName} Virtual Server Block Storage.
+
+For more information, see xref:../storage/container_storage_interface/persistent-storage-csi-ibm-powervs-block.adoc#persistent-storage-csi-ibm-powervs-block[{ibmpowerProductName} Virtual Server Block CSI Driver Operator].
+
 [id="ocp-4-13-secure-execution-z-linux-one"]
 ==== IBM Secure Execution on {ibmzProductName} and {linuxoneProductName}
+
 This feature was introduced as a Technology Preview in
 {product-title} 4.12 and is now generally available in
 {product-title} 4.13.
@@ -247,12 +262,12 @@ For more information, see xref:../installing/disconnected_install/installing-mir
 [id="ocp-4-13-installation-openstack-failure-domains"]
 ==== Deploy clusters that use failure domains on {rh-openstack} (Technology Preview)
 
-You can now deploy clusters that span multiple failure domains on {rh-openstack}. For deployments at scale, failure domains improve resilience and performance. 
+You can now deploy clusters that span multiple failure domains on {rh-openstack}. For deployments at scale, failure domains improve resilience and performance.
 
 // TODO: For more information, see xref :..installing/installing_openstack/installing-openstack-installer-custom.adoc#installation-configuration-parameters-failure-domains-osp_installing-openstack-installer-custom[{rh-openstack} parameters for failure domains].
 
 [id="ocp-4-13-installation-openstack-external-load-balancers"]
-==== Deploy clusters with user-managed load balancers on {rh-openstack} (Technology Preview) 
+==== Deploy clusters with user-managed load balancers on {rh-openstack} (Technology Preview)
 
 You can now deploy clusters on {rh-openstack} with user-managed load balancers rather than the default, internal load balancer.
 
@@ -2510,6 +2525,8 @@ Workaround: By using SSH to connect to the node that is the current leader of th
 +
 To work around this issue, before you update to {product-title} {product-version}, manually remove the `openvswitch2.15` package and install the `openvswitch2.17` package. Then, run the `upgrade.yml` playbook to update {op-system-base} workers and complete the update process. (link:https://issues.redhat.com/browse/OCPBUGS-11677[*OCPBUGS-11677*])
 
+* There is a disk discovery delay when attaching storage to workloads. (link:https://issues.redhat.com/browse/OCPBUGS-11149[*OCPBUGS-11149*])
+
 [id="ocp-4-13-asynchronous-errata-updates"]
 == Asynchronous errata updates