Is a shared envoy for Ingress and Gateway API possible?

[pschichtel]

I have a rather k8s cluster that is rather simple networking wise: Ingress (originally Ingress-Nginx, now Contour) is running on hostPort 443 on two designated nodes and an external TCP loadbalancer routes traffic two either of those nodes. Using hostPorts is basically the only way I can get traffic into the cluster due to firewall restrictions.

Now I want to start using Gateway API for some of the more advanced features of HTTPRoute and friends. My problem is, that a partial transition (some services use gateway, some use ingress) of the cluster would not be possible in this scenario, because I can't have two envoys on the same hostPort.

So: Is there anyway that I can run a single contour instance for both Ingress and Gateway API ? I think the answer is no, but I'm not entirely sure.

If the answer is indeed no, what other options would I have here?

[pschichtel]

I found this which would be possible, but I don't like having an additional hop in the data path. An ingress controller that dynamically translates ingress to gateway objects would be nice, but I don't think that exists.