包阅导读总结
1.
“`
Kubernetes、Node Cgroup Driver、Autoconfiguration、Beta、CRI
“`
2.
Kubernetes 1.31 推出节点 Cgroup 驱动程序的自动配置功能（beta 版），解决了配置 Cgroup 驱动的痛点。v1.28.0 引入相关功能，v1.31.0 此功能为 beta 版，需确保 CRI 实现版本够新且正确配置，未来将取消 kubelet 的 cgroupDriver 配置字段。
3.
– Kubernetes 1.31
– Autoconfiguration For Node Cgroup Driver (beta)
– 历史问题
– 配置正确的 Cgroup 驱动是痛点
– kubelet 和 CRI 实现需配置相同驱动，否则 kubelet 报错
– 新功能
– v1.28.0 引入 KubeletCgroupDriverFromCRI 功能门
– v1.31.0 该功能为 beta 版
– 要求
– CRI 实现版本足够新（containerd v2.0.0、CRI-O v1.28.0）
– 正确配置 CRI 实现的 cgroup_driver
– 未来计划
– 取消 kubelet 的 cgroupDriver 配置字段，CRI 实现不支持将导致 kubelet 无法启动
思维导图：
文章地址：https://kubernetes.io/blog/2024/08/21/cri-cgroup-driver-lookup-now-beta/
文章来源：kubernetes.io
作者：Kubernetes Blog
发布时间：2024/8/21 0:00
语言：英文
总字数：233字
预计阅读时间：1分钟
评分：87分
标签：Kubernetes,Cgroup 驱动,自动化,测试版特性,containerd
以下为原文内容
本内容来源于用户推荐转载，旨在分享知识与观点，如有侵权请联系删除 联系邮箱 media@ilingban.com
Kubernetes 1.31: Autoconfiguration For Node Cgroup Driver (beta)
By Peter Hunt (Red Hat) |
Historically, configuring the correct cgroup driver has been a pain point for users running newKubernetes clusters. On Linux systems, there are two different cgroup drivers:cgroupfs and systemd. In the past, both the kubeletand CRI implementation (like CRI-O or containerd) needed to be configured to usethe same cgroup driver, or else the kubelet would exit with an error. This was asource of headaches for many cluster admins. However, there is light at the end of the tunnel!
Automated cgroup driver detection
In v1.28.0, the SIG Node community introduced the feature gateKubeletCgroupDriverFromCRI, which instructs the kubelet to ask the CRIimplementation which cgroup driver to use. A few minor releases of Kuberneteshappened whilst we waited for support to land in the major two CRI implementations(containerd and CRI-O), but as of v1.31.0, this feature is now beta!
In addition to setting the feature gate, a cluster admin needs to ensure theirCRI implementation is new enough:
- containerd: Support was added in v2.0.0
- CRI-O: Support was added in v1.28.0
Then, they should ensure their CRI implementation is configured to thecgroup_driver they would like to use.
Future work
Eventually, support for the kubelet’s cgroupDriver configuration field will bedropped, and the kubelet will fail to start if the CRI implementation isn’t newenough to have support for this feature.
