-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
Update cAdvisor to v0.37.0 #92919
Update cAdvisor to v0.37.0 #92919
Conversation
/assign @dchen1107 |
/retest |
/retest |
1 similar comment
/retest |
/assign @smarterclayton @liggitt |
/retest |
2 similar comments
/retest |
/retest |
/retest |
3 similar comments
/retest |
/retest |
/retest |
/assign @thockin |
/retest |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dashpole, dchen1107, liggitt 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 |
can I get 1.19 milestone as well? |
/retest |
/milestone 1.19 |
@dashpole: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility. 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. |
@dims can you help with the milestone? |
This is already in the milestone |
cross my fingers 🤞 !! |
ah, my bad |
What type of PR is this?
/kind bug
What this PR does / why we need it:
cAdvisor does a release for each kubernetes release. This is the release for k8s 1.19. It has a number of bug-fixes and improvements.
Because we switched to a different cAdvisor interface for serving prometheus metrics, I had to change a bunch of interfaces in the kubelet. But the behavior is exactly the same.
Does this PR introduce a user-facing change?: