I have been experimenting with the kubernetes Gateway API using kind in Docker
Desktop for macOS. Theoretically I should be able to change implementations
without having to modify my resources - almost. I started with this awesome
Hands-On with the Kubernetes Gateway API: A 30-Minute Tutorial which uses
Gloo Gateway v2 (beta). Under the hood, the edge proxying is done with Envoy,
the same as Istio uses. I managed to work through the Gloo tutorial getting by
with forwarding my curl requests through a kubectl port-forward
but when I
switched over to Istio I found a new problem.