-
Notifications
You must be signed in to change notification settings - Fork 73
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
Disable kubernetes client side rate limiting #352
Disable kubernetes client side rate limiting #352
Conversation
Hi @seankhliao. Thanks for your PR. I'm waiting for a cert-manager member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
/ok-to-test |
We discussed this a bit in the cert-manager standup today (2024-07-25) and we reached the conclusion that this probably wants to live behind a an opt-in flag since API Priority and Fairness is quite new (stable as of k8s v1.29) @wallrj had a plan but I've already forgotten so I'll tag him again here! |
I'll push a command line flag and ping you for a review. |
Trust that server side API Priority and Fairness is enabled on the cluster, which will provide server side rate limiting. This allows a single istio-csr pod to serve larger bursts of traffic, such as when a large number of pods restart. Fixes cert-manager#144 Fixes cert-manager#217 Signed-off-by: Sean Liao <sean@liao.dev>
Signed-off-by: Richard Wall <richard.wall@venafi.com>
Signed-off-by: Richard Wall <richard.wall@venafi.com>
@seankhliao I added a command line option and a Helm chart option to allow this feature to be disable by default, but easily enablable by a Helm chart option. Also rebased the branch to resolve some conflicts with origin/main. |
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
/approve
Making this opt-in makes it very easy to merge. Thanks @seankhliao for this! (and thanks also to Richard for the flag ofc!) 😁
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: SgtCoDFish 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 |
Trust that server side API Priority and Fairness is enabled on the cluster, which will provide server side rate limiting. This allows a single istio-csr pod to serve larger bursts of traffic, such as when a large number of pods restart.
Fixes #144
Fixes #217