update kubeadm cgroup driver documentation once KubeletCgroupDriverFromCRI goes GA

[neolit123]

original k/k ticket:
kubernetes/kubernetes#99808

the new feature gate was added in a previous release and is planned for beta in 1.31:
kubernetes/enhancements#4033

once GA we should remove this page:
https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver/

perhaps SIG node and feature owners will update:
https://kubernetes.io/docs/setup/production-environment/container-runtimes/#cgroup-drivers

users would still be required to pick a driver and configure it on the side of container runtimes (e.g. containerd).

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[pacoxu]

the new feature gate was added in a previous release and is planned for beta in 1.31:
kubernetes/enhancements#4033

This is planned to be beta in this release cycle.

• We may use it if the FG is enabled and the cgroup driver can be detected from the CRI. And we can fall back to our previous logic if not.

[neolit123]

the new feature gate was added in a previous release and is planned for beta in 1.31:
kubernetes/enhancements#4033

This is planned to be beta in this release cycle.

• We may use it if the FG is enabled and the cgroup driver can be detected from the CRI. And we can fall back to our previous logic if not.

i don't think we have any remaining logic for this, do we? we just set the cgroup driver to systemd.

https://github.com/kubernetes/kubernetes/blob/ef9965ebc66dafda37800bb04f5e284535bbba10/cmd/kubeadm/app/componentconfigs/kubelet.go#L194

[neolit123]

KubeletCgroupDriverFromCRI went BETA in 1.31
kubernetes/kubernetes#125828

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[pacoxu]

kubernetes/enhancements#4033 (comment)

• this went to beta in v1.31 and has no plan in v1.32.
• containerd feature Implement RuntimeConfig CRI call containerd/containerd#8722 was merged for 2.0.0(not released yet)
• cri-o cri: implement RuntimeConfig rpc cri-o/cri-o#7079 merged for v1.28 https://github.com/cri-o/cri-o/releases/tag/v1.28.0