Push rate limiting down into rekor client #60
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This requires us to fork a small package from sigstore/rekor, but it gives us a few benefits: We rate limit per HTTP request, which is more aligned with the actual rate limit (rather than per rekor client method call). We rate limit the innermost transport, which means retries won't bypass the limit. We can modify the default transport to use a pooled transport, which should reuse connections, which should be faster with concurrent requests. Signed-off-by: Jon Johnson <jon.johnson@chainguard.dev>
imjasonh
approved these changes
Aug 4, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This requires us to fork a small package from sigstore/rekor, but it gives us a few benefits:
We rate limit per HTTP request, which is more aligned with the actual rate limit (rather than per rekor client method call).
We rate limit the innermost transport, which means retries won't bypass the limit.
We can modify the default transport to use a pooled transport, which should reuse connections, which should be faster with concurrent requests.