Feature Request: Gateway API Support #63
Description
Hi there!
This project strongly advises the use of Contour to take advantage of Envoy. Contour's primary Helm chart is impacted by the recent Bitnami changes.
While the Contour project is forking the original Helm chart and will take over ownership of it, this has piqued my curiosity into moving away from Contour entirely.
Given Gateway API reached its 1.0 release in late 2023, I'm interested in exploring what options we may have with the Gameserver Controller and HTTPRoutes instead of Ingress. This would allow use of projects such as the Envoy Gateway in addition to Contour which also implements the Gateway API.
This has a few benefits:
- A bigger pool of ingress options to work with the project
- Moving configuration of the Fleet's Load Balancer out of the Fleet declaration and into a centralized Gateway configuration should improve the security of any system.
I'm curious for opinions from the maintainers on supporting the Gateway API as a concept and any suggestions for implementation.
My current intent would be to:
- Add additional reconcilers for Gateway API's HttpRoute resource.
- New annotations would be added to toggle between Ingress vs Gateway mode
- Gateway mode would support a GatewayRef resource which would be created as a dependency to installing this project.
- Target Envoy Gateway as the primary Gateway
My concerns are:
- Potential complexities around Gateway API (e.g. different gateways provide many different ways to customize the implementation)
- How to best handle those implementation details if WebSockets do not work out of the box