OSDOCS-15317: add RN entry for GIE and known issue

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

@@ -454,6 +454,11 @@ For more information, see xref:../installing/installing_gcp/installation-config-
 [id="ocp-release-notes-networking_{context}"]
 === Networking
 
+[id="ocp-4-20-networking-gateway-api-ossm-version-bump_{context}"]
+==== Support for Gateway API Inference Extension
+
+{product-title} {product-version} updates {SMProductName} to version 3.1.0, which now supports {rhoai-full}. This version update incorporates essential CVE fixes, resolves other bugs, and upgrades Istio to version 1.26.2 for improved security and performance. See the link:https://docs.redhat.com/en/documentation/red_hat_openshift_service_mesh/3.1/html/release_notes/ossm-release-notes[{SMProductShortName} 3.1.0 release notes] for more information.
+
 [id="ocp-4-20-support-for-bgp-routing-protocol_{context}"]
 ==== Support for the BGP routing protocol
 
@@ -1738,8 +1743,15 @@ In the following tables, features are marked with the following statuses:
 [id="ocp-release-known-issues_{context}"]
 == Known issues
 
+* There is a known issue with Gateway API and {aws-first}, {gcp-first}, and {azure-first} private clusters. The load balancer that is provisioned for a gateway is always configured to be external, which can cause errors or unexpected behavior:
++
+--
+** In an {aws-short} private cluster, the load balancer becomes stuck in the `pending` state and reports the error: `Error syncing load balancer: failed to ensure load balancer: could not find any suitable subnets for creating the ELB`.
 
-
+** In {gcp-short} and {azure-short} private clusters, the load balancer is provisioned with an external IP address, when it should not have an external IP address.
+--
++
+There is no supported workaround for this issue. (link:https://issues.redhat.com/browse/OCPBUGS-57440[OCPBUGS-57440])
 
 
 [id="ocp-telco-core-release-known-issues_{context}"]