-
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
cluster: use systemd cgroup driver for cgroupv2 #111231
Conversation
* Detect if image is using cgroupv2 * Configure both kubelet and containerd to use systemd cgroup driver when running under cgroupv2 Systemd cgroup driver is recommended to be used when running on cgroupv2. It is also the default in moby moby/moby#40846 Signed-off-by: David Porter <david@porter.me>
@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. |
/sig node |
/assign @cheftako |
/test pull-kubernetes-e2e-gce-ubuntu-containerd |
/retest |
|
||
# Use systemd cgroup driver when running on cgroupv2 | ||
local systemdCgroup="false" | ||
if [[ "${CGROUP_CONFIG-}" == "cgroup2fs" ]]; then |
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.
Might be good to add a default value in config-default.sh
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 thought about it, but I don't think it makes sense in this context.
The issue is that we want to default to the systemd cgroup driver when running on cgroupv2 OS image. config-default.sh
sets defaults ahead of time for deployment. At that time, we don't know ahead if the OS image will be cgroupv2 enabled or not.
As a result, this check is done when the VM actually boots which is when we can detect the cgroup configuration. Let me know what you think and if that makes sense.
/test pull-kubernetes-e2e-gce-ubuntu-containerd |
/retest |
/lgtm |
/priority important-soon |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bobbypage, cheftako 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 |
1 similar comment
/retest |
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
What type of PR is this?
/kind feature
What this PR does / why we need it:
when running under cgroupv2
Systemd cgroup driver is recommended to be used when running on
cgroupv2. It is also the default in moby
moby/moby#40846
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.: