Code change:
sudo sysctl --system ``` <del> Verify that the `br_netfilter`, `overlay` modules are loaded by running below instructions: </del> <ins> Verify that the `br_netfilter`, `overlay` modules are loaded by running the following commands: </ins> ```bash lsmod | grep br_netfilter lsmod | grep overlay ``` <del> Verify that the `net.bridge.bridge-nf-call-iptables`, `net.bridge.bridge-nf-call-ip6tables`, `net.ipv4.ip_forward` system variables are set to 1 in your `sysctl` config by running below instruction: </del> <ins> Verify that the `net.bridge.bridge-nf-call-iptables`, `net.bridge.bridge-nf-call-ip6tables`, and `net.ipv4.ip_forward` system variables are set to `1` in your `sysctl` config by running the following command: </ins> ```bash sysctl net.bridge.bridge-nf-call-iptables net.bridge.bridge-nf-call-ip6tables net.ipv4.ip_forward ``` <del> ## Cgroup drivers </del> <ins> ## cgroup drivers </ins> On Linux, {{< glossary_tooltip text="control groups" term_id="cgroup" >}} are used to constrain resources that are allocated to processes. <del> Both {{< glossary_tooltip text="kubelet" term_id="kubelet" >}} and the </del> <ins> Both the {{< glossary_tooltip text="kubelet" term_id="kubelet" >}} and the </ins> underlying container runtime need to interface with control groups to enforce <del> [resource management for pods and containers](/docs/concepts/configuration/manage-resources-containers/) and set resources such as cpu/memory requests and limits. To interface with control </del> <ins> [resource management for pods and containers](/docs/concepts/configuration/manage-resources-containers/) and set resources such as cpu/memory requests and limits. To interface with control </ins> groups, the kubelet and the container runtime need to use a *cgroup driver*. <del> It's critical that the kubelet and the container runtime uses the same cgroup </del> <ins> It's critical that the kubelet and the container runtime use the same cgroup </ins> driver and are configured the same. There are two cgroup drivers available:

Related discussion:
text: This section: I would add information like here: Note: In v1.22, if the user is not setting the cgroupDriver field under KubeletConfiguration, kubeadm will default it to systemd.
this section: already links to: PRs welcome with proposed improvements. /help /sig cluster-lifecycle
If someone wants to help here, I'm not sure what steps they should follow to assist. Because of that: /remove-help
/language en
I think the suggestion is to add something about to container-runtimes pages but I don't think that fits well on that page because it only covers the container runtime side. What could be though is that there's a note/reminder to ensure they are always the same. I can work on that if we agree what's what we want here.
hmm, looks like this is already covered too.
some additional feedback in
/triage accepted
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
/assign