As part of OCP 4.19, Kubernetes Gateway API (GAPI) will be generally available on OCP. This means that OpenShift Service Mesh users will now have platform-level support for GAPI, which was previously only supported in the context of OpenShift Service Mesh(OSSM).

Kubernetes GAPI represents the next generation of APIs used to configure both Kubernetes gateways and Istio (OSSM) traffic management. They will become the default configuration, so we will need to integrate it into our existing documentation - in particular, for gateway creation.

As of OSSM 3.0, we document the use of Gateway API in the Bookinfo example, but do not cover it in our[ Gateways section|https://docs.redhat.com/en/documentation/red_hat_openshift_service_mesh/3.0/html/gateways/ossm-getting-traffic-into-a-mesh#ossm-about-configuring-a-gateway-to-accept-ingress-traffic_ossm-getting-traffic-into-a-mesh.] We need to add a section using Gateway API.

• A relevant PR that updated the current use of Gateway API in the bookinfo example: https://github.com/openshift/openshift-docs/pull/94730/files.

In the sail-operato doc, we have a [small section on this|https://github.com/openshift-service-mesh/sail-operator/blob/main/docs/common/create-and-configure-gateways.md,] but it includes upstream references that we cannot include in product doc. We need an end to end procedure.

This section of the 

Once OCP 4.19 GAs, we will need to update our documentation to:

• Add a procedure to our Gateways section on how to configure a Gateway using Kubernetes GWAPI
• Update the Bookinfo example (linked above) to account for the Gateway API CRDs available in OCP 4.19+.(covered by: https://issues.redhat.com/browse/OSSM-9365)
• Update the Feature Table to set the status of Gateway API CRDs to "GA" for OpenShift Container Platform 4.19 and later releases.

This should be delivered after OCP 4.19 (roughly our OSSM 3.1 / late June 2025), and should be included for both OSSM 3.0 and 3.1 versions of our documentation. It does not block OSSM 3.1.0 though.