Kubernetes v1.36 Enhances Memory Quality of Service with Tiered Protection Mechanism
The latest update to the Memory Quality of Service feature allows Kubernetes to utilize the memory.low and memory.min settings of the cgroup v2 controller. This mechanism ensures that workloads receive tiered protection against reclaim pressure by specifying guaranteed memory levels for individual containers. By defining these thresholds, the kubelet can prevent the kernel from aggressively reclaiming memory from critical processes when the node faces memory pressure.
Related tools
Recommended tools for this topic
These picks prioritize high-intent tools relevant to this topic. Some links may include partner or affiliate tracking.
Strong cloud alternative for startups and developer-led infrastructure decisions.
View DigitalOceanHigh-value hosting and deployment path for frontend and cloud readers.
View VercelA strong security and edge platform match across CDN, Zero Trust, and app protection.
View CloudflareComparison
| Aspect | Before / Alternative | After / This |
|---|---|---|
| Cgroup version | Limited support primarily focused on cgroup v1 | Requirement for cgroup v2 for full Memory QoS |
| Memory protection | Best-effort management without specific kernel hints | Tiered protection using memory.low and memory.min |
| Reclaim behavior | Kernel reclaims memory based on global LRU lists | Kernel respects defined memory floors during reclaim |
| Resource isolation | No clear separation of memory availability guarantees | Explicit isolation levels based on workload priority |
Action Checklist
- Verify Linux nodes are running with cgroup v2 enabled Memory QoS is not compatible with cgroup v1 environments
- Enable the MemoryQoS feature gate in the kubelet configuration This feature is currently in alpha status
- Configure memoryRequest and memoryLimit for critical pods The kubelet uses these values to calculate cgroup settings
- Monitor node-level memory reclaim metrics Ensure that tiered protection is preventing unnecessary OOM events
Source: Kubernetes Blog
This page summarizes the original source. Check the source for full details.
