-
Notifications
You must be signed in to change notification settings - Fork 591
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 RequestRedirect
filter translated to combination of kong plugins
#3702
Conversation
8686891
to
1d753ed
Compare
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #3702 +/- ##
=======================================
- Coverage 73.4% 73.2% -0.2%
=======================================
Files 133 133
Lines 15817 15885 +68
=======================================
+ Hits 11621 11642 +21
- Misses 3443 3480 +37
- Partials 753 763 +10
... and 4 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
7c5afc2
to
b276615
Compare
The Gateway API filter RequestRedirect is now supported and translated to the proper set of kong plugins. Signed-off-by: Mattia Lavacca <lavacca.mattia@gmail.com>
b276615
to
b5046f5
Compare
RequestRedirect
filter translated to combination of kong pluginsRequestRedirect
filter translated to combination of kong plugins
Signed-off-by: Mattia Lavacca <lavacca.mattia@gmail.com>
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.
Approving since points other than https://github.com/Kong/kubernetes-ingress-controller/pull/3702/files#r1131141596 are addressed. That last one I think is a symptom of a broader UX issue that we need to address as GWAPI moves towards GA--I don't think we're handling optional not implemented stuff in any consistent way at present, and there's no immediate way to address it well here, so probably needs an n+1 or n+2 release follow-up.
Not merging immediately given that's maybe an open discussion, but I think a good solution is likely out of scope for 2.9.
What this PR does / why we need it:
Which issue this PR fixes:
Fixes #3673 #2955
Special notes for your reviewer:
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