What is the new cgroup v2 CPU weight formula for Kubernetes?

It's a quadratic map hitting (2,1), (1024,100), (262144,10000) – implemented in runc 1.3.2+ and crun 1.23+.

Will cgroup v1 to v2 conversion break my Kubernetes cluster?

Unlikely for most – but monitoring/tools assuming linear math need fixes. Test post-upgrade.

How do I check if my runtime uses the new formula?

Runc --version or crun --version; look for 1.3.2+ / 1.23+. Inspect pod cgroups via crictl.

Kubernetes' cgroup v2 CPU Fix: Quadratic Magic or Half-Measure?

Picture your Kubernetes pods gasping for CPU cycles, starved by a botched conversion formula. OCI runtimes just dropped a quadratic fix – better, but not without pitfalls.

theAIcatchup Apr 07, 2026 3 min read 10 views

Graph comparing old linear and new quadratic cgroup v1 shares to v2 weight conversion curves

⚡ Key Takeaways

New quadratic formula fixes CPU priority loss and granularity issues in cgroup v2 transitions. 𝕏
Implemented at OCI runtime level (runc/crun), not Kubernetes core – fast adoption possible. 𝕏
Watch for breakage in tools hardcoding old linear weights; test thoroughly. 𝕏

Published by

theAIcatchup

Community-driven. Code-first.

#CPU scheduling

Worth sharing?

Get the best Open Source stories of the week in your inbox — no noise, no spam.

Originally reported by Kubernetes Blog

⚡ Key Takeaways

The 60-Second TL;DR

theAIcatchup

Share this article

Worth sharing?

Related Stories

Kubernetes Just Killed Ingress NGINX: Half Your Clusters Are Suddenly Vulnerable

Uptrack Ditches Databases for Pure BEAM Consensus — And It Actually Works

CI/CD Pipelines: Automating Software's Beating Heart

Kubernetes Pods Stuck in Pending? The Placeholder Trick That Slashes Scale Times by Minutes

Stay in the loop