For my lab, I usually don’t need a specific route pointing to the istio ingress gateway. Neither do I need, for most scenarios, app-specific gateway definitions.

Without gateway injection (available in service mesh 2.3), the routes would have to be created in the same namespace where the “standard” ingress gateway is deployed, or another SMCP-managed gateway.

So, I here’s the setup for a wildcard route and respective istio configs, that is generic, as are my use cases / small apps.