Automated cherry pick of #79245: kunsupported cgroup setup causes kubelet to emit a warning

[saschagrunert]

Cherry pick of #79245 on release-1.15.

#79245: kunsupported cgroup setup causes kubelet to emit a warning

Release note

Fixed possible kubelet stop because of non unified CPU and memory cgroup hierarchy.

[k8s-ci-robot]

@saschagrunert: This PR is not for the master branch but does not have the cherry-pick-approved label. Adding the do-not-merge/cherry-pick-not-approved label.

To approve the cherry-pick, please ping the kubernetes/patch-release-team in a comment when ready.

See also Kubernetes Patch Releases

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.

[saschagrunert]

Do you think we can change the release notes to something like:

Fixed possible kubelet stop because of non unified CPU and memory cgroup hierarchy.

Relates to: #80090

[saschagrunert]

/retest

[saschagrunert]

/test pull-kubernetes-kubemark-e2e-gce-big

[mattjmcnaughton]

/test pull-kubernetes-kubemark-e2e-gce-big
/lgtm

+1 to the note around updating the release note.

[saschagrunert]

/test pull-kubernetes-kubemark-e2e-gce-big

[saschagrunert]

/test pull-kubernetes-kubemark-e2e-gce-big

[saschagrunert]

/retest

[saschagrunert]

Hey @kubernetes/sig-release 👋 do you see a way to get this into the next 1.15 patch release?

[tpepper]

/kind bug
/priority important-soon
@kubernetes/sig-node-pr-reviews looking for ya'll's approval on this cherry pick

[derekwaynecarr]

It would help to understand in the future why we felt this change had to be cherry-picked. Production systems should run a unified hierarchy. If its to support testing 1.15 w/ hack/local-up-cluster that is fine, but Kubernetes systems should run unified hierarchy.

/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: derekwaynecarr, saschagrunert

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:

• cmd/kubelet/OWNERS [derekwaynecarr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[VR-Architect]

I am getting this error on version 1.22.0

[VR-Architect]

This fixed the error from showing for me. Change Docker from cgroupfs to systemd. Would this be good to add to the docs as a step for installation to do this?

Of course, now I have a different error regarding the cni config uninitialized, but that's a different issue.

create a file /etc/docker/daemon.json
{
"exec-opts": ["native.cgroupdriver=systemd"]
}
reference: https://stackoverflow.com/questions/43794169/docker-change-cgroup-driver-to-systemd

reference: #80121

[saschagrunert]

@VR-Architect yeah the systemd cgroup driver should be preferred over cgroupfs. Unfortunately docker shim got deprecated a while ago, but having the information in the docs should be useful.