diff --git a/release_notes/ocp-4-19-release-notes.adoc b/release_notes/ocp-4-19-release-notes.adoc
index e8d0cbe91a85..e2eef1ce852e 100644
--- a/release_notes/ocp-4-19-release-notes.adoc
+++ b/release_notes/ocp-4-19-release-notes.adoc
@@ -2809,6 +2809,40 @@ To save the `vmcore` file, use the `crashkernel` setting to reserve 1024 MB of m
 
 * NFS volumes exported from VMware vSAN Files cannot be mounted by clusters running {product-title} 4.19 due to RHEL-83435. To avoid this issue, ensure that you are running VMware ESXi and vSAN at the latest patch versions of 8.0 P05, or later. (link:https://issues.redhat.com/browse/OCPBUGS-55978[OCPBUGS-55978])
 
+Known Gateway API issues
+
+* By default, `istiod` will create a ConfigMap `istio-ca-root-cert` in every namespace it watches, which can create unnecessary ConfigMaps. (link:https://issues.redhat.com/browse/OSSM-9076[OSSM-9076])
+
+* When using Gateway API via the Cluster Ingress Operator (CIO), any Istio specific resources (e.g. VirtualService) are not allowed or supported. (link:https://issues.redhat.com/browse/OSSM-9154[OSSM-9154])
+
+* Istio will copy all labels and annotations from your Gateway objects to the child resources it creates. (link:https://issues.redhat.com/browse/OSSM-8989[OSSM-8989])
+
+* Gateway API on CIO can be broken by an existing  incompatible OpenShift Service Mesh (OSSM) subscription. (link:https://issues.redhat.com/browse/NE-1964[NE-1964])
+
+* Currently Gateway API is not supported for on-premise platforms: BareMetal, VSphere, oVirt, KubeVirt, EquinixMetal, Nutanix. (link:https://issues.redhat.com/browse/NE-2010[NE-2010])
+
+* The reverse proxy for Gateway API is known to be less performant than HAProxy. (link:https://issues.redhat.com/browse/NE-1990[NE-1990])
+
+* Gateway API may not work with RH Connectivity Link, OpenShift AI, or other layered products. (link:https://issues.redhat.com/browse/NE-1967(NE-1967))
+
+* Gateway API does not have idling support. (link:https://issues.redhat.com/browse/NE-1103[NE-1103])
+
+* Gateway API does not have OpenShift Console integration. (link:https://issues.redhat.com/browse/NE-1109[NE-1109])
+
+* Gateway API has no OpenShift Console command line integration. (link:https://issues.redhat.com/browse/NE-1102[NE-1102])
+
+* Gateway API has no configuration of access logs or other Istio options. (link:https://issues.redhat.com/browse/NE-1926[NE-1926])
+
+* Gateway API does not currently support using User Defined Networks (UDN). (link:https://issues.redhat.com/browse/NE-1928[NE-1928])
+
+* Users will not receive flags when previous Gateway API CRDs are trying to make changes. (link:https://issues.redhat.com/browse/NE-1958[NE-1958])
+
+* Installing OSSM with Gateway API causes an Ingress Operator Failure. (link:https://issues.redhat.com/browse/OCPBUGS-55317[OCPBUGS-55317])
+
+* On a private cluster, the LB created for a Gateway should be internal, but it is external. (link:https://issues.redhat.com/browse/OCPBUGS-57440[OCPBUGS-57440])
+
+* Users who create a Gateway resource pointing to the correct `GatewayClass` must also manually add an `istio.io/rev` label to their Gateway object for it to be recognized. (link:https://issues.redhat.com/browse/OSSM-10518[OSSM-10518])
+
 [id="ocp-4-19-asynchronous-errata-updates_{context}"]
 == Asynchronous errata updates