add support to dynamically set the kubelet loglevel #14799
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: rphillips The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
rphillips
force-pushed
the
fixes/add_kubelet_loglevel_support
branch
from
250981c to
198ec27
Compare
|
/retest |
|
@rphillips: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
@rphillips: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
going to migrate this to ci-operator/step-registry /close |
|
related to #10053 |
|
@rphillips: Closed this PR. DetailsIn 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. |
3 participants
Adds an optional
KUBELET_LOG_LEVEL[integer 1..10] parameter to the e2e tests. If the variable is not set, then the default loglevel (2, currently) is selected. If the KUBELET_LOG_LEVEL is overwritten, then manifests are injected to raise/lower the loglevel.Log Level 3 or 4: These levels can be used to debug the kubelet. Anything higher than 3 (and certainly 4) might introduce other performance related issues on nodes.