This site uses cookies for analytics via Microsoft Clarity. We only enable it after your consent. See our Privacy Policy.
Sujith Quintelier
  • Resume
  • Archives
  • Taxonomy
    • Tags
    • Categories
    • Series
  • Tools
    • CIDR Calculator
    • Certification Renewal Tracker
    • Tech Radar
    • UBB Simulator
  • Updates
  • Legal
    • Contact
    • About
    • Privacy
    • Cookies
  • linkedin
  • github
  • twitter
  • mastodon
  • bsky
  • facebook
  • instagram
  • buymeacoffee

  • Toggle theme

Back to updates

Memory QoS - 1

2026 (2)

October (1)

k8s: The Shift to cgroup v2 in Kubernetes: What You Need to Know

Kubernetes Official Blog

2026-10-06

Kubernetes is deprecating cgroup v1 and is moving toward cgroup v2 as the default path: in v1.35, kubelet startup fails by default on cgroup v1 nodes, and kubeadm preflight checks now error on v1.35+ when v1 is detected. The post also summarizes cgroup v2-related behaviors and features in Kubernetes 1.36, including Memory QoS, container-scoped OOM handling, PSI metrics, and in-place pod-level resource updates.

September (1)

k8s: Kubernetes v1.37: Memory QoS Graduates to Beta

Kubernetes Official Blog

2026-09-14

Kubernetes v1.37 makes Memory QoS Beta and turns it on by default, but it does not change runtime behavior unless you explicitly set throttling or reservation fields. The main config change is that `memoryThrottlingFactor` now defaults to `null`, so existing clusters will not start writing `memory.high` unless they already set it.

© Copyright 2018-Present Sujith Quintelier All Rights Reserved • RSS

Privacy • Cookies • Contact

Based on Bootstrap. Icons from Bootstrap Icons and Font Awesome. Web fonts from Google.

Source Code