[Feature Request] Support service discovery for Kubernetes Gateway API #4021
-
DescriptionSimilar to IngressRoute from Traefik, it would be very nice to support the Gateway API, which is intended to replace both Ingress and IngressRoute. OtherNo response |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 9 replies
-
Hi @Exeteres . I have created a PR for this feature here #4289. Currently pending review. |
Beta Was this translation helpful? Give feedback.
-
I would also be interested into this feature. It would be a nice addition to the project. Especially since the Kubernetes team has stabilized most of the APIs and that many Kubernetes projects already support it (or, at least, are almost done supporting it).
I have to correct you about this, though : it isn't there to replace Ingress and IngressRoute. It is there as an alternative way to expose services. |
Beta Was this translation helpful? Give feedback.
-
I'm also interested into this feature. Usage of the Gateway API is on the rise right now. |
Beta Was this translation helpful? Give feedback.
-
I just stumbled across this before submitting my own feature request. I see that the PR was closed due to "not meeting the requirements in terms of community interest." That seems a bit myopic... I looked at the code, and there are some things to address (namely the conditional checks, since this isn't an either/or to @Bricklou's point that GAPI isn't meant to replace Ingress), but I think we should push forward with the change. I can help review and test. |
Beta Was this translation helpful? Give feedback.
-
This discussion has been automatically closed because it was marked as answered. See our contributing guidelines for more details. |
Beta Was this translation helpful? Give feedback.
hi @dudo. See PR #4643.