-
Notifications
You must be signed in to change notification settings - Fork 39.7k
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
Move grpc rate limiter from podresource folder #121019
Conversation
/assign @SergeyKanzhelev |
I'm fine with generalizing, but I want to point out that this rate-limiting was tailor-made for podresources, so it enshrines some key assumptions and implicit values that can make the aforementioned generalization nontrivial. I'll review the changeset ASAP. |
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.
/lgtm
I have my reservations about reusing this code easily, but I can't see anything wrong with this change, and the new location IMO is a sidegrade wrt the old location.
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.
one last typo please - it's admittedly minor, but the churn to fix later is, out of experience, actually bigger. Other than that LGTM
Rate limitter.go file is a generic file implementing grpc Limiter interface. This file can be reuse by other gRPC API not only by podresource. Change-Id: I905a46b5b605fbb175eb9ad6c15019ffdc7f2563
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.
/lgtm
thanks for all your updates!
LGTM label has been added. Git tree hash: 09e809c4ae903b8b324c38e93df2c56e067635cc
|
let's make sure existing podresources e2e tests they all pass. Should be no brainer. |
failure not relevant for lane |
/test |
@ffromani: The
The following commands are available to trigger optional jobs:
Use
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/test pull-kubernetes-node-kubelet-serial-containerd |
failures can be unrelated and are not necessarily blocking for this PR (unless the lane is |
yes, this is the same failure in issue |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kl52752, mrunalp The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
@kl52752: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Rate limiter.go file is a generic file implementing grpc Limiter interface. This file can be reuse by other gRPC API not only by podresource.
Change-Id: I905a46b5b605fbb175eb9ad6c15019ffdc7f2563
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
Rate Limit interface will be used by KEP, moving this file outside the podresource folder so it can be reused.