Daniel Loader

The response from istio is fairly sane so not sure what to I can add to the issue. Ultimately the ambient service mesh has to be the outer encapsulation of...

Thanks for trying, I guess fundamentally we're trying to fight the design of the service mesh - in a pinch I'll just have to disable the ambient mesh for the...

Would this be less terrible with nftables or is iptables not the actual pain here?

> okay, can't find any worthy workaround, let's set a requirement for ambient mesh to use privileged. I don't think it's unreasonable to expect privileged access in this particular scenario.

I have this issue but no symlinks involved, just trying to open both the local repo specific Taskfile.yml and my global user Taskfile.yml in the $HOME. I imagine the extension...

Still happening for me with 2.10+

Feels like it'll need a new issue then, this is quite an important design and implementation point, if you can provision httpRoutes with hostnames, and those hostnames _aren't necessarily_ a...

> We managed to circumvent this issue by creating separate listeners within the same Gateway for different hostnames. Yeah this is just simply unworkable in complex environments, my gateway object...

Yeah good call though it's still under proposal if you're using a Gateway API implementing solution like I am. https://github.com/kubernetes-sigs/gateway-api/pull/3213 So maybe if this gets approved I can roll with...

Just as an update for the thread, the mismatch between External-DNS ([which looks for HTTPRoute hostnames](https://kubernetes-sigs.github.io/external-dns/v0.14.2/tutorials/gateway-api/#hostnames)) and Cert-manager which works on the Gateway objects has become quite the pain. The...