-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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 Limit Quota #19793
Rate Limit Quota #19793
Conversation
CC @envoyproxy/api-shepherds: Your approval is needed for changes made to |
@tyxia As discussed IRL, please take a look. |
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.
Thanks for doing this!
Please let me know if you have any questions. Thanks!
api/envoy/extensions/filters/http/rate_limit_quota/v3/rate_limit_quota.proto
Outdated
Show resolved
Hide resolved
api/envoy/extensions/filters/http/rate_limit_quota/v3/rate_limit_quota.proto
Show resolved
Hide resolved
api/envoy/extensions/filters/http/rate_limit_quota/v3/rate_limit_quota.proto
Outdated
Show resolved
Hide resolved
api/envoy/extensions/filters/http/rate_limit_quota/v3/rate_limit_quota.proto
Outdated
Show resolved
Hide resolved
api/envoy/extensions/filters/http/rate_limit_quota/v3/rate_limit_quota.proto
Outdated
Show resolved
Hide resolved
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.
Thanks for working on this! Some comments from me on the first pass.
PS: Oops. Just noticed some comments are overlapped with Mark's. Those were in my earlier draft(shown in edited history). Forgot to refresh the page before sending out the draft.
api/envoy/extensions/filters/http/rate_limit_quota/v3/rate_limit_quota.proto
Outdated
Show resolved
Hide resolved
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.
Thanks for iterating on this!
I haven't gone through the PR thoroughly yet but want to send some comments for early discussion.
api/envoy/extensions/filters/http/rate_limit_quota/v3/rate_limit_quota.proto
Show resolved
Hide resolved
api/envoy/extensions/filters/http/rate_limit_quota/v3/rate_limit_quota.proto
Show resolved
Hide resolved
api/envoy/extensions/filters/http/rate_limit_quota/v3/rate_limit_quota.proto
Outdated
Show resolved
Hide resolved
api/envoy/extensions/filters/http/rate_limit_quota/v3/rate_limit_quota.proto
Outdated
Show resolved
Hide resolved
/assign @tyxia |
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.
Making good progress!
Please let me know if you have any questions. Thanks!
api/envoy/extensions/filters/http/rate_limit_quota/v3/rate_limit_quota.proto
Outdated
Show resolved
Hide resolved
api/envoy/extensions/filters/http/rate_limit_quota/v3/rate_limit_quota.proto
Outdated
Show resolved
Hide resolved
api/envoy/extensions/filters/http/rate_limit_quota/v3/rate_limit_quota.proto
Outdated
Show resolved
Hide resolved
api/envoy/extensions/filters/http/rate_limit_quota/v3/rate_limit_quota.proto
Outdated
Show resolved
Hide resolved
We need a non-Googler to do API review here as well. Unassigning myself as API shepherd. Suggest @mattklein123 takes a look as someone with rate limit domain experience. |
I have a high level question before diving into the review. Should this be built into the existing global rate limit filter? It seems like there is a lot of overlap? If this has been discussed somewhere else please let me know and I can take a look. Thank you. |
Matt, what we're building here wound up being a whole new protocol with somewhat different semantics to the existing RLS protocol. I think it makes more sense to make it a new filter rather than trying to shoe-horn it into the existing one. I suspect the two would not have much code in common. |
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.
/wait
api/envoy/extensions/filters/http/rate_limit_quota/v3/rate_limit_quota.proto
Outdated
Show resolved
Hide resolved
api/envoy/extensions/filters/http/rate_limit_quota/v3/rate_limit_quota.proto
Outdated
Show resolved
Hide resolved
api/envoy/extensions/filters/http/rate_limit_quota/v3/rate_limit_quota.proto
Outdated
Show resolved
Hide resolved
api/envoy/extensions/filters/http/rate_limit_quota/v3/rate_limit_quota.proto
Outdated
Show resolved
Hide resolved
api/envoy/extensions/filters/http/rate_limit_quota/v3/rate_limit_quota.proto
Outdated
Show resolved
Hide resolved
api/envoy/extensions/filters/http/rate_limit_quota/v3/rate_limit_quota.proto
Outdated
Show resolved
Hide resolved
@markdroth @mattklein123 I'm trying to figure out how to best move forward with this extensions. Looking at the protocols as they now, they are quite different and I do not see an easy way to make them compatible. There are maybe some way to make bucket and descriptor specification compatible, not sure how much would be gained from this. Would it make sense to then brand this filter such that it is Google specific? I.e. |
Got it, thanks! Sorry for the inconvenience. |
Signed-off-by: Sergii Tkachenko <sergiitk@google.com>
@mattklein123 All set! Ready for another round. |
Signed-off-by: Sergii Tkachenko <sergiitk@google.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.
Thanks LGTM with one remaining comment. Thank you!
/wait
api/envoy/extensions/filters/http/rate_limit_quota/v3/rate_limit_quota.proto
Outdated
Show resolved
Hide resolved
Signed-off-by: Sergii Tkachenko <sergiitk@google.com>
Signed-off-by: Sergii Tkachenko <sergiitk@google.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.
Thanks!
@mattklein123 We didn't coordinate removing the filter - will make a separate PR right now. |
RLQS API added in envoyproxy#19793. This change removes the docs and adds [#not-implemented-hide:] tags until the implementation is ready. Signed-off-by: Sergii Tkachenko <sergiitk@google.com>
RLQS API added in #19793. This change removes the docs and adds [#not-implemented-hide:] tags until the implementation is ready. Signed-off-by: Sergii Tkachenko <sergiitk@google.com>
RLQS API added in envoyproxy/envoy#19793. This change removes the docs and adds [#not-implemented-hide:] tags until the implementation is ready. Signed-off-by: Sergii Tkachenko <sergiitk@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 3af90c11e40ecf175aaa830a5e1daebd15551b54
RLQS API added in envoyproxy/envoy#19793. This change removes the docs and adds [#not-implemented-hide:] tags until the implementation is ready. Signed-off-by: Sergii Tkachenko <sergiitk@google.com>
This is an alternative to existing RLS, redesigned for streaming.
Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]