4033: update to GA

Signed-off-by: Peter Hunt <pehunt@redhat.com>

Author: haircommander

content/en/docs/reference/command-line-tools-reference/feature-gates/KubeletCgroupDriverFromCRI.md

@@ -13,15 +13,27 @@ stages:
   - stage: beta
     defaultValue: true
     fromVersion: "1.31"
+  - stage: stable
+    defaultValue: true
+    fromVersion: "1.34"
 ---
 Enable detection of the kubelet cgroup driver
 configuration option from the {{<glossary_tooltip term_id="cri" text="CRI">}}.
-You can use this feature gate on nodes with a kubelet that supports the feature gate
-and where there is a CRI container runtime that supports the `RuntimeConfig`
-CRI call. If both CRI and kubelet support this feature, the kubelet ignores the
+This feature gate is now on for all clusters. However, it only works on nodes
+where there is a CRI container runtime that supports the `RuntimeConfig`
+CRI call. If the CRI supports this feature, the kubelet ignores the
 `cgroupDriver` configuration setting (or deprecated `--cgroup-driver` command
-line argument). If you enable this feature gate and the container runtime
+line argument). If the container runtime
 doesn't support it, the kubelet falls back to using the driver configured using
 the `cgroupDriver` configuration setting.
+The kubelet will stop falling back to this configuration in Kubernetes 1.36.
+Thus, users must upgrade their CRI container runtime to a version that supports
+the `RuntimeConfig` CRI call by then. Admins can use the metric
+`kubelet_cri_losing_support` to see if there are any nodes in their cluster that
+will lose support in 1.36. The following CRI versions support this CRI call:
+
+* containerd: Support was added in v2.0.0
+* CRI-O: Support was added in v1.28.0
+
 See [Configuring a cgroup driver](/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver)
-for more details.
+for more details.

content/en/docs/reference/command-line-tools-reference/kubelet.md

@@ -420,7 +420,7 @@ JobBackoffLimitPerIndex=true|false (BETA - default=true)<br/>
 JobManagedBy=true|false (ALPHA - default=false)<br/>
 JobPodReplacementPolicy=true|false (BETA - default=true)<br/>
 JobSuccessPolicy=true|false (BETA - default=true)<br/>
-KubeletCgroupDriverFromCRI=true|false (BETA - default=true)<br/>
+KubeletCgroupDriverFromCRI=true|false (STABLE - default=true)<br/>
 KubeletCrashLoopBackOffMax=true|false (ALPHA - default=false)<br/>
 KubeletFineGrainedAuthz=true|false (ALPHA - default=false)<br/>
 KubeletInUserNamespace=true|false (ALPHA - default=false)<br/>

content/en/docs/setup/production-environment/container-runtimes.md

@@ -153,6 +153,14 @@ enabled and a container runtime that supports the `RuntimeConfig` CRI RPC,
 the kubelet automatically detects the appropriate cgroup driver from the runtime,
 and ignores the `cgroupDriver` setting within the kubelet configuration.
 
+However, older versions of container runtimes (specifically,
+containerd 1.y and below) do not support the `RuntimeConfig` CRI RPC, and
+may not respond correctly to this query, and thus the Kubelet falls back to using the
+value in its own `--cgroup-driver` flag.
+
+In Kubernetes 1.36, this fallback behavior will be dropped, and older versions
+of containerd will fail with newer kubelets.
+
 {{< caution >}}
 Changing the cgroup driver of a Node that has joined a cluster is a sensitive operation.
 If the kubelet has created Pods using the semantics of one cgroup driver, changing the container