Nick Young

Okay, thanks for that. From what I can see from the Gateway API objects, and the Services, everything seems to be set up fine as far as Cilium is concerned....

I think this is a good idea, but unfortunately, I think we need to _add_ the new version, and move the `v1alpha2` source files to _mostly_ be aliases to the...

This is because I _know_ that people are using TLSRoute in production. I know they shouldn't be, but they definitely are, and we will screw them over very hard if...

@rostislavbobo Yeah, I think that's fine. The intent here was to end up with the generated YAML having both versions, to save users from a breaking change when they install...

Part of it will be fixed, yes. But This one has proven _way_ more difficult than I thought, still working on it.

#9207 may also be relevant here, because if a Gateway has UDPRoutes and TCPRoutes attached to the same Gateway on the same port number (could be a different Listener though),...

@danieljkemp there are two reasons: - it's not really the intended way to use a Gateway. You shouldn't be afraid of having multiple Gateways, and keeping the separate use cases...

@zodd3131, thanks for the details. In this case, do you expect the Gateway to have a Listener per TCPRoute? That is, that each TCPRoute forwards traffic from a single port?...

I should note that the Gateway API spec supports using TLSRoute with `Terminate` TLS mode - which means that you can have multiple TLSRoutes share the same TLS port, discriminated...

@chifu1234, when asking for Proxy protocol, what do you mean? Do you mean that you want a TCP stream forwarded directly to the backend Service? In that case, Cilium's Loadbalancer...