-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Added event-qps and event-burst flags to kubelet #10486
Added event-qps and event-burst flags to kubelet #10486
Conversation
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
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. |
Welcome @DOboznyi! |
Hi @DOboznyi. Thanks for your PR. I'm waiting for a kubernetes 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/test-infra repository. |
d2211de
to
fce5028
Compare
Thanks for this. |
Maybe better to set it to 5. Because 0 can provide a security issue from my perspective. It will make it unlimited. |
I think the CIS check is there because if you rate limit, important events can be missed. Thus the
Setting it to 5 will retain current behaviour, which is also fine. |
baec44b
to
a0f082c
Compare
b67fc82
to
7126076
Compare
@olemarkus, you are completely right. Where could i add default value as 0? I'm not familiar with kops code base. |
b765ded
to
fd00614
Compare
@olemarkus I changed default value to 0. Could you review PR again? |
/ok-to-test |
Thanks @DOboznyi. Looks good from my point of view. @olemarkus any thoughts before merging? |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: DOboznyi, hakman 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 |
One more thing @DOboznyi, could you squash the commits? |
Change default value for event-qps to 0 Added event-burst parametr Signed-off-by: Dmytro Oboznyi <dobozniy@gmail.com>
1053faf
to
334ff1d
Compare
@hakman done, all commits squashed. |
@hakman do you have any ideas why test failed? |
/retest |
Flake, no worries. :) |
From the second attempt test passed. Is it ready to merge now? |
/lgtm |
…-upstream-release-1.19 Automated cherry pick of #10486: Added event-qps to kubelet flags Change default value for
#6356 Enable kubelet --event-qps flag.
#6150 Will provide the functionality to fix
[WARN] 4.2.9 Ensure that the --event-qps argument is set to 0 or a level which ensures appropriate event capture (Not Scored)
in kube-bench report (CIS benchmarks)