Problem: How do I expose a service deployed within a service mesh, such that it can be accessed from outside the mesh? Answer: Use an Ingress Gateway! There are multiple ways to install and configure an Ingress Gateway though.

Determine if the Gateway Configuration information in the readme file should be moved to the 3.0 core docs repo.

Equally important, the TP1 doc should discuss Gateway Configuration, including both ingress and egress gateways. So, even if we do not migrate what's in the readme, we will still have some doc work for TP1.

Ways to expose services outside the mesh:

1. Creating a gateway using Gateway Injection (Should be similar to OSSM 2 Gateway Injection content, though with the new operator resources - Istio rather than SMCP, etc) + using an OpenShift route (should be similar to IOR migration doc in OSSM 2 with new operator)
2. Creating a gateway using Gateway API
3. Expose a gateway using a LoadBalancer Service

An older blog post that outlines the trade offs between method 1 and 3 (method 2 didn't exist at the time it was written): https://www.redhat.com/en/blog/design-considerations-at-the-edge-of-the-servicemesh