Skip to content
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

extensions: add http bandwidth limit filter #14096

Closed
wants to merge 53 commits into from

Conversation

nitgoy
Copy link
Contributor

@nitgoy nitgoy commented Nov 19, 2020

Commit Message: adds bandwidth limit filter core functionality and UTs
Additional Description: the filter smoothens the flow of data in both direction up to the specified bandwidth limit.
Risk Level:
Testing: UTs added. Adding more UTs and integration tests.
Docs Changes: Pending
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #13604]
[Optional Deprecated:]

@repokitteh-read-only
Copy link

Hi @nitgoy, welcome and thank you for your contribution.

We will try to review your Pull Request as quickly as possible.

In the meantime, please take a look at the contribution guidelines if you have not done so already.

🐱

Caused by: #14096 was opened by nitgoy.

see: more, trace.

@repokitteh-read-only
Copy link

CC @envoyproxy/api-shepherds: Your approval is needed for changes made to api/envoy/.
CC @envoyproxy/api-watchers: FYI only for changes made to api/envoy/.

🐱

Caused by: #14096 was opened by nitgoy.

see: more, trace.

Copy link
Member

@tonya11en tonya11en left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great!

You'll want to see how other filters implement their config as an alpha version so the proto isn't locked in.

Let's use this PR for the whole filter review! I'll stand by for the rest of it. Thanks for doing this.

@nitgoy nitgoy force-pushed the bandwidthlimitproto branch from 1526a7e to 1f11d00 Compare December 2, 2020 05:09
nitgoy and others added 7 commits December 3, 2020 19:14
Signed-off-by: Nitin <nigoyal@microsoft.com>
Signed-off-by: Nitin <nigoyal@microsoft.com>
Signed-off-by: Nitin <nigoyal@microsoft.com>
Signed-off-by: Nitin <nigoyal@microsoft.com>

Signed-off-by: Nitin Goyal <nrk.goyal@gmail.com>
Signed-off-by: Nitin <nigoyal@microsoft.com>

Signed-off-by: Nitin Goyal <nrk.goyal@gmail.com>
Signed-off-by: Nitin <nigoyal@microsoft.com>

Signed-off-by: Nitin Goyal <nrk.goyal@gmail.com>
nitgoy added 5 commits January 5, 2021 18:54
…m rate limiter

Signed-off-by: Nitin <nigoyal@microsoft.com>
Signed-off-by: Nitin <nigoyal@microsoft.com>
…ate limiter

Signed-off-by: Nitin <nigoyal@microsoft.com>
Signed-off-by: Nitin <nigoyal@microsoft.com>
Signed-off-by: Nitin <nigoyal@microsoft.com>
Base automatically changed from master to main January 15, 2021 23:01
@nitgoy
Copy link
Contributor Author

nitgoy commented Jan 26, 2021

As suggested, I've created two separate PRs:
Token bucket: #14827
Stream rate limiter: #14828

Hope to get those merged while I address the remaining comments here.

@mattklein123
Copy link
Member

Sorry I haven't looked at this yet, but will put this in waiting until the base PRs are merged and then we can circle back.

/wait

@leoribeiro2
Copy link

leoribeiro2 commented Mar 10, 2021

Hi guys!
Have you any updates about that feat?

@nitgoy

@github-actions
Copy link

This pull request has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 7 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions!

@github-actions github-actions bot added the stale stalebot believes this issue/PR has not been touched recently label Apr 10, 2021
@nitgoy
Copy link
Contributor Author

nitgoy commented Apr 11, 2021

Hi guys!
Have you any updates about that feat?

@nitgoy

Sorry it's taken so long. We're now using it for our product so that helped to uncover some functional issues. Hoping to push out new changes pretty soon. Most likely after completing this dependent PR: #14828

@github-actions github-actions bot removed the stale stalebot believes this issue/PR has not been touched recently label Apr 12, 2021
Signed-off-by: Nitin Goyal <nigoyal@microsoft.com>
@mattklein123 mattklein123 removed their assignment Apr 16, 2021
nitgoy added 2 commits April 22, 2021 14:24
Signed-off-by: Nitin Goyal <nigoyal@microsoft.com>
Signed-off-by: Nitin Goyal <nigoyal@microsoft.com>
Signed-off-by: Nitin Goyal <nigoyal@microsoft.com>
@nitgoy nitgoy marked this pull request as ready for review May 4, 2021 21:56
nitgoy added 3 commits May 5, 2021 22:39
Signed-off-by: Nitin Goyal <nigoyal@microsoft.com>
Signed-off-by: Nitin Goyal <nigoyal@microsoft.com>
Signed-off-by: Nitin Goyal <nigoyal@microsoft.com>
@nitgoy
Copy link
Contributor Author

nitgoy commented May 6, 2021

I have opened a replacement PR for this one after addressing most of the comments: #16358. I was running into some DCO issues which were getting non-trivial to fix. Please take a look at the new PR, will close this one.

@nitgoy nitgoy closed this May 6, 2021
@nitgoy nitgoy deleted the bandwidthlimitproto branch June 3, 2021 20:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

how to config bandwidth limit
5 participants