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
[release-4.4] Bug 1811713: Specify cgroups in kubelet.conf so cAdvisor stats will be tracked #1546
[release-4.4] Bug 1811713: Specify cgroups in kubelet.conf so cAdvisor stats will be tracked #1546
Conversation
Specifying runtimeCgroups will cause the Kubelet to monitor statistics for the specified cgroup so that we have statistics for crio. Specifying systemCgroups will cause the Kubelet to monitor statistics for system processes and make that data available in our metrics pipeline. Specifying cgroupRoot explicitly is required when specifying systemCgroups
@openshift-cherrypick-robot: This pull request references Bugzilla bug 1806027, which is invalid:
Comment 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. |
/retitle [release-4.4] Bug 1811713: Specify cgroups in kubelet.conf so cAdvisor stats will be tracked |
@openshift-cherrypick-robot: This pull request references Bugzilla bug 1811713, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 6 validation(s) were run on this bug
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. |
/retest |
/hold I don't think this actually fixed anything, after looking at the 4.5 latest. |
@smarterclayton the CI tests were broken for most of the weekend and the master PR only merged early AM Sunday. Are you sure that image builds happened in time for the version you tested on? Are you seeing the cgroup changes in your nodes' kubelet.conf files?
I am seeing them like that on the 4.5 cluster that I just now installed. Are you not able to see info from cadvisor? I am:
|
/hold cancel We had a race in builds that prevented the latest version from getting pushed until the next build ran. Steve and I will track that down. This PR was manually verified and it has the data I expect. |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: openshift-cherrypick-robot, rphillips 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 Please review the full test history for this PR and help us cut down flakes. |
3 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@openshift-cherrypick-robot: All pull requests linked via external trackers have merged. Bugzilla bug 1811713 has been moved to the MODIFIED state. 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. |
This is an automated cherry-pick of #1540
/assign joelsmith