OSDOCS-15776 Gateway API: Backport of known issues

Author: jmanthei

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

@@ -2809,6 +2809,20 @@ 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])
+
 [id="ocp-4-19-asynchronous-errata-updates_{context}"]
 == Asynchronous errata updates