sorry for the vague title, but the following common scenarios are not encompassed is the docs, making it difficult for customer to understand how to configure this integration:

1. istio ingress gateway is directly exposed. This makes a lot of sense, as it is really useless to have two reverse proxies one inf front of the other. So the customer will have a load balancer, pointing to the istio ingress proxy and a dedicate wildcard domain.
2. using the non-default ingress gateway, again it's very likely that a mesh will have different ingress gateways dedicated to different use cases, the serverless deployment will likely get a dedicated gateway. This is actually partially discussed in the current docs, where it asks to ascertain that the gateway is usable (https://docs.openshift.com/serverless/1.33/integrations/serverless-ossm-setup.html#serverless-ossm-verifying-installation-prerequisites_serverless-ossm-setup), but it does not offer solutions when the gateway is not usable.
3.  non-default domain. Again if there is a ingress gateway directly expose via load balancer, then it will have a dedicate wildcard domain. The docs do not explain how to customize the domain at the serverless deployment level, the docs only discuss how to override a domain at the individual service level