-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
vendor: Bump cAdvisor to v0.43.0 #106282
vendor: Bump cAdvisor to v0.43.0 #106282
Conversation
@bobbypage: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
Bumping cAdvisor from v0.39.2 -> v0.43.0 * Also pin transitive dependencies * containerd v1.4.9 -> v1.4.11 * docker v20.10.2+incompatible> v20.10.7+incompatible Signed-off-by: David Porter <david@porter.me>
* Change cAdvisor manager constructor * Change call to adding AcceleratorUsageMetrics Signed-off-by: David Porter <david@porter.me>
c7c66bf
to
b6269ce
Compare
/kind bug |
/assign @dims |
github.com/containerd/containerd/api/services/containers/v1 | ||
github.com/containerd/containerd/api/services/tasks/v1 | ||
github.com/containerd/containerd/api/services/version/v1 | ||
github.com/containerd/containerd/api/types | ||
github.com/containerd/containerd/api/types/task | ||
github.com/containerd/containerd/containers |
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.
nice set of cleanups! yay. the rest of github.com/containerd/containerd
will get cleaned out when we remove dockershim for sure. (or the change in moby/moby we are waiting on)
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.
/approve
/lgtm
/assign @liggitt |
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
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.
I'm curious if any of bug fixes worth mentioning in release notes for k8s. I see it was like this without release notes most of the time
/lgtm
/approve for deps |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bobbypage, dims, harche, liggitt, SergeyKanzhelev 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 |
backport to v1.20? @bobbypage |
@dims @liggitt @SergeyKanzhelev Should this be backported to 1.19-1.22 as the bump included bug fixes for metrics? |
google/cadvisor#2956 actually ended up being reverted in cAdvisor google/cadvisor#2964 |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Bump cAdvisor to v0.43.0.
Changes: google/cadvisor@v0.39.2...v0.43.0
and cAdvisor release notes have PRs included: https://github.com/google/cadvisor/releases
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: