-
Notifications
You must be signed in to change notification settings - Fork 33
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
Rate limiting limits controller #527
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #527 +/- ##
===========================================
- Coverage 80.20% 57.97% -22.24%
===========================================
Files 64 80 +16
Lines 4492 5973 +1481
===========================================
- Hits 3603 3463 -140
- Misses 600 2173 +1573
- Partials 289 337 +48
Flags with carried forward coverage won't be shown. Click here to find out more.
|
0344fe4
to
63bee9a
Compare
63bee9a
to
8297900
Compare
8297900
to
db8fe5c
Compare
8c08d25
to
c026986
Compare
c026986
to
77e1247
Compare
Closing in favor of #893 I leave the branch undeleted because there are some integration tests that can be backported |
What
Custom controller for Limitador limits reading from DAG Gateway API topology and RateLimitPolicies
Limitador cluster envoy filter controller reading from DAG Gateway API topology and RateLimitPolicies
Kuadrant rate limiting controllers no longer depends on back references annotation:
kuadrant.io/ratelimitpolicies
. Instead, controllers rely on the DAG Gateway API topopology to read cluster state. Kuadrant rate limiting controller responsible for the limitador's limits is also based on this approach. So is the limitador cluster envoy filter controllerFix reconciliation event blind spots due to race conditions or timing issues. The reconciled resource reflects latest updates from the cluster (Gateways, Routes and policies).
Work being done as part of #530