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

Add unit multiplier #552

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Conversation

harpunius
Copy link

@harpunius harpunius commented Apr 6, 2024

Implements the unit multiplier idea suggested in #190.

rate_limit:
  unit: <second, minute, hour, day>
  requests_per_unit: <uint>
  unit_multiplier: <uint | optional>

I chose to force unit multiplier to 1 if the value is unset to avoid if/else checks whenever we rely on the value or log anything. This means the PR got slightly bigger than intended, but I think it's nicer.

The config parser panics if unit_multiplier: 0 is set. One RFC is the TODO in UnitToDividerWithMultiplier where I added a redundant if-zero runtime check to make sure we don't multiply by zero and effectively disable the rate limiting.

Note, this is a draft and doesn't build due to the dependencies on both https://github.com/envoyproxy/go-control-plane/blob/main/envoy/service/ratelimit/v3/rls.pb.go#L357-L367 and https://github.com/envoyproxy/go-control-plane/blob/main/ratelimit/config/ratelimit/v3/rls_conf.pb.go#L246-L263. I opened an issue to track this: envoyproxy/envoy#33277.

I couldn't run the integration tests locally (WSL setup) so let me know if we need to extend those tests as well.

Happy to hear your thoughts.

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 label May 10, 2024
@harpunius
Copy link
Author

Not stale. Still waiting for input from e.g. @mattklein123

@github-actions github-actions bot removed the stale label May 13, 2024
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 label Jun 12, 2024
@harpunius
Copy link
Author

Still waiting for input.

@github-actions github-actions bot removed the stale label Jun 18, 2024
@dnbn
Copy link

dnbn commented Jul 2, 2024

Hello @harpunius thanks It appears that one check were not successful.
Thank you for your implementation proposal. Do you know when it can be merged?

@ramaraochavali
Copy link

@harpunius are you actively working on this? If not we would like to contribute this as this is needed for us

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 label Aug 29, 2024
@harpunius
Copy link
Author

Not stale, still waiting for input envoyproxy/envoy#33277.

@github-actions github-actions bot removed the stale label Aug 29, 2024
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 label Sep 28, 2024
@ramaraochavali
Copy link

Not stale

@github-actions github-actions bot removed the stale label Sep 30, 2024
@Pawan-Bishnoi
Copy link

@harpunius is draft still the correct status of this PR?
(asking because that's probably the reason it isn't seeing much traction)

Tobias Sommer added 2 commits September 30, 2024 11:12
@harpunius
Copy link
Author

Hey, thanks for your input and interest in this PR.

As mentioned in the PR description:

Note, this is a draft and doesn't build due to the dependencies on both https://github.com/envoyproxy/go-control-plane/blob/main/envoy/service/ratelimit/v3/rls.pb.go#L357-L367 and https://github.com/envoyproxy/go-control-plane/blob/main/ratelimit/config/ratelimit/v3/rls_conf.pb.go#L246-L263. I opened an issue to track this: envoyproxy/envoy#33277.

For my implementation we need to extend the ratelimit protobuf definitions linked above. Tests run locally by statically linking the fixed protobuf files (with the new field added, see the issue in envoyproxy/envoy). Unfortunately, I don't see a way around that due to how the ratelimit envoy filter communicates with the ratelimit service.

I opened an issue to track this, but I still haven't gotten a response from the maintainers. I'm not very skilled with c++, so I'm having a hard time figuring out what additional work is needed in envoyproxy/envoy, for instance https://github.com/envoyproxy/envoy/blob/f580ed067db0f2a48085aa33e45a3a9cf5e36bfe/source/extensions/filters/http/ratelimit/ratelimit_headers.cc#L32 also needs to reflect the unit multiplier.

I did rebase so there at least aren't merge conflicts any more :)

@Pawan-Bishnoi
Copy link

ah, I see.
So you are waiting to someone to update the rls proto in envoy. And only after that you will be able to merge your changes to this repo.

Makes sense. Let me see if I can move the envoy piece.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants