ce the breaking changes in Istio 1.20.</p><h2 id=problem-to-solve>Problem to solve</h2><p>The currently documented egress gateway use-cases rely on the fact that the target of the traffic
(the hostname) is statically configured in a <code>VirtualService</code>, telling Envoy in the egress gateway pod where to TCP proxy
the matching outbound connections. You can use multiple, and even wildcard, DNS names to match the routing criteria, but you
are not able to route the traffic to the exact location specified 