diff --git a/release_notes/ocp-4-13-release-notes.adoc b/release_notes/ocp-4-13-release-notes.adoc
index d1eace874d3b..b82949e866b2 100644
--- a/release_notes/ocp-4-13-release-notes.adoc
+++ b/release_notes/ocp-4-13-release-notes.adoc
@@ -221,6 +221,20 @@ This release introduces support for the following features when local OCI catalo
 
 For more information, see xref:../installing/disconnected_install/installing-mirroring-disconnected.adoc#oc-mirror-oci-format_installing-mirroring-disconnected[Including local OCI Operator catalogs].
 
+[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. 
+
+// 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) 
+
+You can now deploy clusters on {rh-openstack} with user-managed load balancers rather than the default, internal load balancer.
+
+// TODO: For more information, see xref :../installing/installing_openstack/installing-openstack-installer-custom.adoc#install-osp-external-lb-config_installing-openstack-installer-custom[Installation configuration for a cluster on OpenStack with a user-managed load balancer].
+
 [id="ocp-4-13-post-installation"]
 === Post-installation configuration
 
@@ -465,6 +479,18 @@ For more information about OVN-Kubernetes as a secondary network, see xref:../ne
 
 In {product-title} {product-version}, `nodeSelector` has been added to the egress firewall destination spec in OVN-Kubernetes network plug-in. This feature allows users to add a label to one or multiple nodes and the IP addresses of the selected nodes are included in the associated rule. For more information, see xref:../networking/ovn_kubernetes_network_provider/configuring-egress-firewall-ovn.adoc#configuringNodeSelector-example_configuring-egress-firewall-ovn[Example nodeSelector for EgressFirewall]
 
+[id="ocp-4-13-nw-openstack-kuryr-migration"]
+==== Kuryr to OVN-Kubernetes migration procedure for clusters that run on {rh-openstack} (Technology Preview)
+
+You can now migrate a cluster that runs on {rh-openstack} and uses Kuryr to OVN-Kubernetes.
+
+// TODO: For more information, see xref :../networking/ovn_kubernetes_network_provider/migrate-from-kuryr-sdn.adoc#migrate-from-kuryr-sdn[Migrating from the Kuryr network plugin to the OVN-Kubernetes network plugin].
+
+[id="ocp-4-13-nw-openstack-egressip"]
+==== Improved egress IP support for clusters that run on {rh-openstack}
+
+For clusters that run on {rh-openstack} and use OVN-Kubernetes, manually reassigning floating IP addresses for reservation ports is no longer necessary. If a reservation port is removed from one node and recreated on another one, the reassignment now happens automatically.
+
 [id="ocp-4-13-storage"]
 === Storage
 
@@ -1019,7 +1045,7 @@ In the following tables, features are marked with the following statuses:
 
 |Kuryr on {rh-openstack}
 |General Availability
-|General Availability
+|Deprecated
 |Deprecated
 
 |====
@@ -1080,7 +1106,7 @@ CoreDNS will stop supporting wildcard DNS queries for names under the `cluster.l
 [id="ocp-4-13-ne-kuryr"]
 ==== Kuryr support for clusters that run on {rh-openstack}
 
-In {product-title} 4.12, support for Kuryr on clusters that run on {rh-openstack} is deprecated. Support will be removed no earlier than {product-title} 4.14.
+In {product-title} 4.12, support for Kuryr on clusters that run on {rh-openstack} was deprecated. Support will be removed no earlier than {product-title} 4.14.
 
 [id="ocp-4-13-icsp"]
 ==== `ImageContentSourcePolicy` objects
@@ -1927,12 +1953,12 @@ In the following tables, features are marked with the following statuses:
 
 |Support for {rh-openstack} DCN
 |Technology Preview
-|Technology Preview
-|Technology Preview
+|General Availability
+|General Availability
 
 |Support for external cloud providers for clusters on {rh-openstack}
 |Technology Preview
-|Technology Preview
+|General Availability
 |General Availability
 
 |====