Open 0xDones opened 4 months ago
To add to this, I think it would be very helpful to look at building a Gateway API implementation, and consider providing a small controller for the Ingress API that reuses as much of the HTTPRoute controller as possible.
https://gateway-api.sigs.k8s.io/
Looking through the core codebase, I think the bones to support Pingora as the data plane for a Gateway API implementation could already do TLSRoute, HTTPRoute, and TCPRoute.
This is pretty exciting :)
It's more likely that River will have a Kubernetes Ingress implementation: https://github.com/memorysafety/river
This question has been stale for a week. It will be closed in an additional day if not updated.
I dropped the question
and stale
label. This issue is a legitimat feature request.
The stale bot is only meant to close question
issues which usually have no clear bug or feature request to report.
What is the problem your feature solves, or the need it fulfills?
Is there any future plan to support deploying an ingress controller on Kubernetes that uses Pingora? We have controllers for other services like Nginx, HAProxy, and many others.
Describe the solution you'd like
Create an ingress controller implementation so we have another option when deploying ingress controllers to K8s. This would definitely increase Pingora's adoption by the community.
Describe alternatives you've considered
None
Additional context