-
Notifications
You must be signed in to change notification settings - Fork 592
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: don't configure Kong Gateways with incompatible router flavor #5040
base: main
Are you sure you want to change the base?
feat: don't configure Kong Gateways with incompatible router flavor #5040
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #5040 +/- ##
=======================================
- Coverage 75.4% 75.4% -0.1%
=======================================
Files 167 167
Lines 18906 18942 +36
=======================================
+ Hits 14273 14287 +14
- Misses 3803 3823 +20
- Partials 830 832 +2 ☔ View full report in Codecov by Sentry. |
51acbbb
to
d164a57
Compare
@@ -22,14 +23,14 @@ func TestValidateRoots(t *testing.T) { | |||
name string | |||
configStr string | |||
expectedDBMode string | |||
expectedRouterFlavor string | |||
expectedRouterFlavor configuration.RouterFlavor |
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.
Will wait for #5092 to not cause conflicts
Waiting for #5092 to reuse the introduced |
On hold for now pending the work on Gateway side (slack thread link in #5018's description): summary #5018 (comment). |
What this PR does / why we need it:
Warn users in logs when Kong Gateway with incompatible router is detected and reject the client for that Gateway when sending out the configuration.
Which issue this PR fixes:
Related: #5018
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