OSDOCS-15477: add gwapi aws known issue

Author: jldohmann

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

@@ -2775,6 +2775,14 @@ 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 that prevents the provisioning of internal load balancers on {aws-first}, {gcp-first}, and {azure-first} private clusters. Load balancers configured for internal use are incorrectly determined to be external:
+
+** In an {aws-short} private cluster, the load balancer becomes stuck in the `pending` status 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, but the existence of an external IP address is unexpected.
+
+As a workaround, you can manually add an annotation to the load balancer service. For example, for an {aws-short} load balancer, add the annotation: `service.beta.kubernetes.io/aws-load-balancer-internal="true"`. (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`.
@@ -3048,4 +3056,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].