Update Ingress vs Gateway API notice (#8251)

A customer was confused by the wording of the note, and wasn't sure if it was referring to the API of the Kong Gateway or the Kubernetes API Gateway API. This text attempts to clarify, and make it clearer that we are simply supporting the best practice patterns of the community. --------- Co-authored-by: lena-larionova <[email protected]>
Kong · Dec 11, 2024 · dfa7ad0 · dfa7ad0
1 parent 8683506
commit dfa7ad0
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/app/_src/kubernetes-ingress-controller/concepts/ingress.md b/app/_src/kubernetes-ingress-controller/concepts/ingress.md
@@ -6,7 +6,7 @@ purpose: |
 ---
 
 {:.note}
-> **Note**: Kong will support the Ingress resource for the foreseeable future. However, Kong recommends that you use Gateway API resources to configure networking in Kubernetes.
+> **Note**: Kong will continue to support the [Kubernetes Ingress resource](https://kubernetes.io/docs/concepts/services-networking/ingress/) to configure a {{site.base_gateway}} for the foreseeable future. However, as the [Kubernetes Gateway API resource](https://kubernetes.io/docs/concepts/services-networking/gateway/) is now the preferred mechanism for configuring inbound routing in Kubernetes clusters, we recommend that you use the Gateway API to configure a {{site.base_gateway}}.
 
 The {{site.kic_product_name}} uses ingress classes to filter Kubernetes Ingress objects and other resources before converting them into Kong configuration. This allows it to coexist with other ingress controllers and/or other deployments of the {{site.kic_product_name}} in the same cluster. A {{site.kic_product_name}} only processes configuration marked for its use.