… To avoid downtime, you will need to migrate those nodes to systems where cgroup v2 is enabled. To learn more, read about cgroup v2 ; you can also track the switchover work via KEP-5573: Remove cgroup v1 support . …
… Cgroup v1 enters the maintenance mode As Kubernetes continues to evolve and adapt to the changing landscape of container orchestration, the community has decided to move cgroup v1 support into maintenance mode in v1.31. …
… In v1.36, the Kubelet now detects OS-level PSI support via cgroup configurations before reporting. …
… This work was done as part of KEP 3902 led by SIG Scheduling and SIG Node. New features in Beta This is a selection of some of the improvements that are now beta following the v1.34 release. …
… With some distributions now defaulting to this API, Kubernetes must support it to continue operating on those distributions. cgroups v2 offers several improvements over cgroups v1, for more information see the cgroups v2 documentation. …
… This work was done across several KEPs including 4671 , 5547 , 5832 , 5732 , and 5710 led by SIG Scheduling and SIG Apps. Features graduating to Stable This is a selection of some of the improvements that are now stable following the v1.36 release. …
… PSI Pressure Stall Information metrics for scheduling improvements This feature adds support on Linux nodes for providing PSI stats and metrics using cgroupv2. It can detect resource shortages and provide nodes with more granular control for pod scheduling. …
… This improvement is particularly beneficial in clusters with high Pod churn or frequent scheduling failures, ensuring a more efficient and resilient scheduling process. This work was done as a part of KEP 4832 by SIG Scheduling . …
… Quality of Service for memory resources Originally, Kubernetes used the v1 cgroups API. With that design, the QoS class for a Pod only applied to CPU resources such as cpu shares . As an alpha feature, Kubernetes v1.22 can now use the cgroups v2 API to control memory allocation and isolation. …