Merge pull request #96578 from jldohmann/OSDOCS-15477-4.19

[enterprise-4.19] OSDOCS-15477: add gwapi aws known issue

Author: jldohmann

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

@@ -2782,6 +2782,16 @@ After you run the command, the CNO collects `must-gather` logs that you can insp
 +
 (link:https://issues.redhat.com/browse/OCPBUGS-52367[OCPBUGS-52367])
 
+* 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-ran-4-19-known-issues_{context}"]
 
 * In the event of a crash, the `mlx5_core` NIC driver causes an out-of-memory issue and `kdump` does not save the `vmcore` file in `/var/crash`.
@@ -3088,4 +3098,4 @@ $ oc adm release info 4.19.0 --pullspecs
 
 [id="ocp-4-19-0-updating_{context}"]
 ==== Updating
-To update an {product-title} 4.19 cluster to this latest release, see xref:../updating/updating_a_cluster/updating-cluster-cli.adoc#updating-cluster-cli[Updating a cluster using the CLI].
+To update an {product-title} 4.19 cluster to this latest release, see xref:../updating/updating_a_cluster/updating-cluster-cli.adoc#updating-cluster-cli[Updating a cluster using the CLI].