Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please email the CNCF helpdesk: helpdesk@rt.linuxfoundation.org

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: bradtopol

Assign the PR to them by writing /assign @bradtopol in a comment when ready.

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Deploy preview for kubernetes-io-master-staging ready!

Built with commit a4a6001

https://deploy-preview-9410--kubernetes-io-master-staging.netlify.com

@erickhun thank you for you contribution.

kubeadm only sets the cgroup driver automatically in the case of Docker. all other CRI remain using cgroupfs which is the default value of the kubelet.

instead of removing this section modify it to:

## Configure cgroup driver used by kubelet on Master Node

When using Docker, kubeadm will detect the cgroup driver for the kubelet
automatically and set in the file `/var/lib/kubelet/kubeadm-flags.env`
on runtime.

If you are using a different CRI, you have to modify the the drop-in file
`/etc/systemd/system/kubelet.service.d/10-kubeadm.conf`, by adding
`--cgroup-driver=<driver-name>`.

Please mind, that you **only** have to do that if the cgroup driver of your CRI
is not `cgroupfs`, because that is the default value in the kubelet already.

/cc @kubernetes/sig-cluster-lifecycle-pr-reviews @Bradamant3
^ comments / edits on the above?
/hold

/assign

sent new PR for this:
#9541

/close