-
Notifications
You must be signed in to change notification settings - Fork 38.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
fix error of setting negative value for containerLogMaxSize #99680
Conversation
Hi @CaoDonghui123. 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. |
I have verified the #99650. The kubelet will started normally when the negative value quoted by double quotation. |
d937ba2
to
0d01174
Compare
ping @ehashman @andrewsykim |
ping @wzshiming |
@CaoDonghui123 We are in code-freeze for 1.21 |
/ok-to-test |
/triage accepted |
/assign @sjenning |
|
/test pull-kubernetes-e2e-kind-ipv6 |
/retest |
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CaoDonghui123, 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 |
…f-#99680-upstream-release-1.20 Automated cherry pick of #99680: fix error of setting negative value for containerLogMaxSize
…f-#99680-upstream-release-1.21 Automated cherry pick of #99680: fix error of setting negative value for containerLogMaxSize
…f-#99680-upstream-release-1.19 Automated cherry pick of #99680: fix error of setting negative value for containerLogMaxSize
What type of PR is this?
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #99650
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: