Dep bump to runc 1.1.0, cadvisor 0.44.0#109029
Dep bump to runc 1.1.0, cadvisor 0.44.0#109029k8s-ci-robot merged 2 commits intokubernetes:masterfrom
Conversation
There was a problem hiding this comment.
This one appears to be unavoidable... runc has a direct dep on it https://github.com/opencontainers/runc/blob/86d6898f3052acba1ebcf83aa2eae3f6cc5fb471/go.mod#L17
There was a problem hiding this comment.
Yes, libseccomp-golang did not made a release since 2019, and the released version is no longer adequate (mostly due to seccomp-notify functionality which runc now supports/requires)
|
/test pull-kubernetes-node-kubelet-serial-containerd |
|
/milestone v1.24 |
|
The dependency change LGTM. Please assign to Jordan when this is green as i don't have root OWNERS approval thanks! |
|
/lgtm |
|
Thanks for rebasing this @ehashman and @kolyshkin for the update! |
|
/test pull-kubernetes-node-e2e-containerd |
|
Flake was #109082 - filed bug |
|
/approve /lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ehashman, liggitt, mrunalp, odinuge The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This updates vendored runc/libcontainer to 1.1.0, and google/cadvisor to a version updated to runc 1.1.0 (google/cadvisor#3048). Changes in vendor are generated by (roughly): ./hack/pin-dependency.sh github.com/google/cadvisor v0.44.0 ./hack/pin-dependency.sh github.com/opencontainers/runc v1.1.0 ./hack/update-vendor.sh ./hack/lint-dependencies.sh # And follow all its recommendations. ./hack/update-vendor.sh ./hack/update-internal-modules.sh ./hack/lint-dependencies.sh # Re-check everything again. Co-Authored-By: Kir Kolyshkin <[email protected]>
The changes (mostly in pkg/kubelet/cm) are there to adopt changed
runc 1.1 API, and simplify things a bit. In particular:
1. simplify cgroup manager instantiation, using a new, easier way of
libcontainers/cgroups/manager.New;
2. replace libcontainerAdapter with a boolean variable (all it did
was passing on whether systemd manager should be used);
3. trivial change due to removed cgroupfs.HugePageSizes and added
cgroups.HugePageSizes();
4. do not calculate cgroup paths in update / destroy, since libcontainer
cgroup managers now calculate the paths upon creation (previously,
they were doing that only in Apply, so using e.g. Set or Destroy right
after creation was impossible without specifying paths).
We currently still calculate cgroup paths in Exists -- this is to be
addressed separately.
Co-Authored-By: Elana Hashman <[email protected]>
|
/lgtm |
|
/retest-required |
|
OK, runc 1.1.1 is now out, and this is a PR to replace this one (no changes other than rebase and use runc 1.1.1 instead of 1.1.0): #109091 |
|
Will it be backported to 1.22 and 1.23 branches? |
What type of PR is this?
/kind cleanup
/priority important-soon
/sig node
/cc @odinuge @dims @mrunalp
What this PR does / why we need it:
Non-draft rebased follow-up to #107149
This updates vendored runc/libcontainer to 1.1.0,
and google/cadvisor to a version updated to runc 1.1.0
(google/cadvisor#3048).
Changes in vendor are generated by (roughly):
The changes (mostly in pkg/kubelet/cm) are there to adopt changed
runc 1.1 API, and simplify things a bit. In particular:
simplify cgroup manager instantiation, using a new, easier way of
libcontainers/cgroups/manager.New;
replace libcontainerAdapter with a boolean variable (all it did
was passing on whether systemd manager should be used);
trivial change due to removed cgroupfs.HugePageSizes and added
cgroups.HugePageSizes();
do not calculate cgroup paths in update / destroy, since libcontainer
cgroup managers now calculate the paths upon creation (previously,
they were doing that only in Apply, so using e.g. Set or Destroy right
after creation was impossible without specifying paths).
We currently still calculate cgroup paths in Exists -- this is to be
addressed separately.
Which issue(s) this PR fixes:
none
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: