[WIP] update runc to 1.1.0-rc.1#107016
Conversation
|
Skipping CI for Draft Pull Request. |
|
@kolyshkin: 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 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. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: kolyshkin 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 |
|
/remove-sig api-machinery |
fdab5c3 to
aae7ecc
Compare
|
/remove-sig api-machinery |
|
/retest |
2002645 to
85febb8
Compare
|
/remove-sig api-machinery |
|
/retest |
85febb8 to
1df3b21
Compare
|
/retest |
1df3b21 to
68c87fb
Compare
|
/retest |
This updates vendored runc/libcontainer to 1.1.0-rc.1, and google/cadvisor to a version in google/cadvisor#3031. Changes in vendor are generated by (roughly): ./hack/pin-dependency.sh github.com/google/cadvisor=github.com/kolyshkin/cadvisor runc-1.1.0-rc1 ./hack/pin-dependency.sh github.com/opencontainers/runc v1.1.0-rc.1 ./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. Changes in pkg/kubelet/cm are to adopt new runc 1.1 libcontainer/cgroups APIs and build on its impovements. In particular: - simplify cgroup manager instantiation, using a new, easier way (i.e. libcontainers/cgroups/manager.New); - the fact that 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). - trivial change due to removed cgroupfs.HugePageSizes and added cgroups.HugePageSizes(). Signed-off-by: Kir Kolyshkin <[email protected]>
Signed-off-by: Kir Kolyshkin <[email protected]>
68c87fb to
ee22f6d
Compare
|
/retest |
|
@kolyshkin: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. |
|
/remove-sig api-machinery |
|
Closing in favor of #107149 which lay things out in a more digestible way. |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This updates vendored runc/libcontainer to 1.1.0-rc.1
(release notes at https://github.com/opencontainers/runc/releases/tag/v1.1.0-rc.1)
and google/cadvisor to a version in google/cadvisor#3031.
Changes in vendor are generated by (roughly):
Changes in pkg/kubelet/cm are to adopt new runc 1.1 libcontainer/cgroups
APIs and build on its impovements. In particular:
simplify cgroup manager instantiation, using a new, easier way
(i.e. libcontainers/cgroups/manager.New);
the fact that 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).
trivial change due to removed cgroupfs.HugePageSizes and added
cgroups.HugePageSizes().
Which issue(s) this PR fixes:
none
Special notes for your reviewer:
With this PR, I am also trying to untangle the mess of both setting cgroups.Path
(or name+parent in case of systemd) and providing pre-calculated cgroups paths,
which confuses anyone reading the code.
Previously, this was required since cgroup managers were only calculating the paths
in Apply, and so using Set or Destroy right after instantiation was impossible. This was
solved in opencontainers/runc#3216 and so it is not required
to specify paths.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: