-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Limit to X requests/sec PER CUSTOMER using LocalRateLimit #23351
Comments
This is an often-requested feature for local rate limiting, an ability to specify a "wildcard" bucket instead of "literal" values, e.g. #19895. |
I would like to work on it. |
@vikaschoudhary16 I'm interested as well. Is the LocalRateLimit extension written in C++? Do you have a link to the source? I'd be happy to collaborate. |
@skbergam the entry points (the responsible filter code (HTTP and TCP (network)), including how it is configured):
The common implementation (used by both filters above as lib): https://github.com/envoyproxy/envoy/tree/main/source/extensions/filters/common/local_ratelimit |
sure. Not able to find you on envoy slack channel. What is your slack id? |
|
Interested in learning about the progress made on this feature. Would be really valuable to my use case! |
/assign |
Title: Limit to X requests/sec PER CUSTOMER using LocalRateLimit
Description:
Can we add support to the LocalRateLimit feature for specifying a blanket limit for each customer in this way? In my case, I can trust round robin load balancing to evenly distribute, so I'm fine just dividing my limit by the number of nodes and calling it good.
The text was updated successfully, but these errors were encountered: