diff --git a/release_notes/ocp-4-5-release-notes.adoc b/release_notes/ocp-4-5-release-notes.adoc
index 10a8d35de050..ea7d694d6ec8 100644
--- a/release_notes/ocp-4-5-release-notes.adoc
+++ b/release_notes/ocp-4-5-release-notes.adoc
@@ -175,6 +175,25 @@ been introduced in Ironic. You can now provision bare metal hosts using IPv6
 with Ironic. The `snpnoly.efi` bootloader executable and compatible iPXE
 binaries are now included in the `tftpboot` directory.
 
+[id="ocp-4-5-openstack-custom-networking"]
+==== Custom networks and subnets for clusters on {rh-openstack}
+
+{product-title} {product-version} introduces support for installing clusters on {rh-openstack-first}
+ that rely on preexisting networks and subnets.
+
+[id="ocp-4-5-openstack-additional-networks"]
+==== Additional networks for clusters on {rh-openstack}
+
+{product-title} {product-version} introduces support for multiple networks in clusters that run on {rh-openstack}.
+You can specify these networks for both control plane and compute machines during installation.
+
+[id="ocp-4-5-openstack-kuryr-octavia"]
+==== Improved {rh-openstack} load balancer upgrade experience for clusters that use Kuryr
+
+Clusters that use Kuryr now have improved support for Octavia load-balancing services on {rh-openstack} clusters that were upgraded from 13 to 16. For example, these clusters now support the Octavia OVN provider driver.
+
+For more information, see xref:../installing/installing_openstack/installing-openstack-installer-kuryr.html#installation-osp-kuryr-octavia-driver_installing-openstack-installer-kuryr[The Octavia OVN driver].
+
 [id="ocp-4-5-security"]
 === Security
 
@@ -252,6 +271,11 @@ cluster installation by sharing the node's pull secret credentials with the
 
 {product-title} {product-version} introduces the Vertical Pod Autoscaler Operator (VPA). The VPA reviews the historic and current CPU and memory resources for containers in Pods and can update the resource limits and requests based on the usage values it learns. You create individual custom resources (CR) to instruct the VPA to update all of the Pods associated with a workload object, such as a Deployment, Deployment Config, StatefulSet, Job, DaemonSet, ReplicaSet, or ReplicationController. The VPA helps you to understand the optimal CPU and memory usage for your Pods and can automatically maintain Pod resources through the Pod lifecycle.
 
+[id="ocp-4-5-openstack-anti-affinity"]
+==== Anti-affinity compute node scheduling on {rh-openstack}
+
+If separate physical hosts are available on an {rh-openstack} deployment, compute nodes will be scheduled across all of them.
+
 [id="ocp-4-5-cluster-monitoring"]
 === Cluster monitoring