In anticipation of OpenShift Service Mesh 3, we are asking customers to move off of the default gateways created and managed by the SMCP with the Istio control plane (ie the Gateways + related routes you get out of the box when you install OSSM) to Gateways that are created via either:

a) Gateway Injection (as documented and supported in 2.5) + OpenShift route creation without IOR.

b) Gateway API gateways (which will be supported in 2.6 via https://issues.redhat.com/browse/OSSM-5854)

We should provide some documented guidance on how to make this transition while minimizing application traffic impact. Some impact may be unavoidable, and we should note that.

This came up as a question in a Service Mesh AMA call on April 2nd. We should try to target 2.6 for this.