OSDOCS-15776 Gateway API: Backport of known issues

Author: jmanthei

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

@@ -2809,6 +2809,14 @@ 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])
 
+* By default, `istiod` will create a ConfigMap `istio-ca-root-cert` in every namespace it watches, which can create unnecessary ConfigMaps. This behavior depends on the discoverySelectors, so that any proxy that might be injected in those namespaces has istiod's CA root certificate. This is needed for the proxies to verify the istiod's certificate when performing the initial connection. No 'normal' sidecar injections are planned. The only injection necessary is Gateway injection based on k8s Gateway API resources. This issue was fixed for Red Hat OpenShift Service Mesh 3.0.1. However, istiod does not clean up existing 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])
+
+* Two gateways can specify the same host name and are not marked as conflicted.
+
 [id="ocp-4-19-asynchronous-errata-updates_{context}"]
 == Asynchronous errata updates