-
Notifications
You must be signed in to change notification settings - Fork 590
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(gateway-api): matching routes by Listener.AllowedRoutes
#3181
Conversation
Listener.AllowedRoutes
50461f0
to
6078573
Compare
6078573
to
3330303
Compare
3330303
to
f66db93
Compare
f66db93
to
281300e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The matching host step always returns false for TCPRoute
and UDPRoute
. I do not know if this is expected.
Adding do not merge label as I'm not sure about the supported kinds from listeners status ad whether those should be taken into account |
Seems like it makes sense to take |
What this PR does / why we need it:
This PR implements matching listeners by Listener.AllowedRoutes as well as some refactor in
getSupportedGatewayForRoute
Which issue this PR fixes:
Should fix #2408
Special notes for your reviewer:
This PR also adds matching routes against listener's status and most specifically
.SupportedKinds
. I'm not sure if that's the right thing to do given the comment in the spec but it surely feels right. For now in such cases we'd add agatewayv1beta1.RouteReasonNotAllowedByListeners
.PR Readiness Checklist:
Complete these before marking the PR as
ready to review
:CHANGELOG.md
release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR