@@ -157,7 +157,7 @@ Starting with v1.22 and later, when creating a cluster with kubeadm, if the user
157
157
the ` cgroupDriver` field under `KubeletConfiguration`, kubeadm defaults it to `systemd`.
158
158
{{< /note >}}
159
159
160
- In Kubernetes {{< skew currentVersion >}} , with the `KubeletCgroupDriverFromCRI`
160
+ In Kubernetes v1.28 , with the `KubeletCgroupDriverFromCRI`
161
161
[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
162
162
enabled and a container runtime that supports the `RuntimeConfig` CRI RPC,
163
163
the kubelet automatically detects the appropriate cgroup driver from the runtime,
@@ -257,7 +257,7 @@ sudo systemctl restart containerd
257
257
When using kubeadm, manually configure the
258
258
[ cgroup driver for kubelet] ( /docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver/#configuring-the-kubelet-cgroup-driver ) .
259
259
260
- In Kubernetes {{< skew currentVersion >}} , you can enable automatic detection of the
260
+ In Kubernetes v1.28 , you can enable automatic detection of the
261
261
cgroup driver as an alpha feature. See [ systemd cgroup driver] ( #systemd-cgroup-driver )
262
262
for more details.
263
263
@@ -302,7 +302,7 @@ You should also note the changed `conmon_cgroup`, which has to be set to the val
302
302
cgroup driver configuration of the kubelet (usually done via kubeadm) and CRI-O
303
303
in sync.
304
304
305
- In Kubernetes {{< skew currentVersion >}} , you can enable automatic detection of the
305
+ In Kubernetes v1.28 , you can enable automatic detection of the
306
306
cgroup driver as an alpha feature. See [ systemd cgroup driver] ( #systemd-cgroup-driver )
307
307
for more details.
308
308
0 commit comments