Mastering Memory QoS in Kubernetes v1.36: Tiered Memory Protection Explained
Memory QoS exists to address the challenges of memory management in Kubernetes. As applications scale, ensuring that critical workloads have guaranteed memory while allowing for flexibility in less critical ones becomes essential. Memory QoS achieves this by using the cgroup v2 memory controller, allowing you to specify hard and soft memory protections for your pods.
At its core, Memory QoS utilizes four key interfaces: memory.max for hard limits, memory.min for guaranteed protection (only for Guaranteed Pods), memory.low for soft protection (for Burstable Pods), and memory.high for throttling. The kubelet plays a crucial role by maintaining memory.min across the kubepods root cgroup and memory.low for Burstable QoS cgroups. You can configure Memory QoS through the kubelet configuration, enabling it with featureGates.MemoryQoS and specifying the memoryReservationPolicy to control how memory is reserved.
In production, understanding how to set these parameters effectively is key. Ensure your Kubernetes version is v1.36 or later, and ideally, use a kernel version of 5.9 or higher to avoid known issues like the kernel livelock. The Memory QoS feature is still in alpha, so be prepared for potential changes and ensure thorough testing before rolling it out to critical environments.
Key takeaways
- →Enable Memory QoS by setting featureGates.MemoryQoS to true in your kubelet configuration.
- →Use memory.min for Guaranteed Pods to ensure hard memory protection.
- →Implement memory.low for Burstable Pods to provide soft memory protection.
- →Monitor memory metrics using the command: curl -sk https://localhost:10250/metrics | grep memory_qos.
- →Be aware of kernel compatibility; use kernel 5.9 or higher to avoid livelock issues.
Why it matters
In production, Memory QoS can significantly improve resource allocation, ensuring critical applications remain responsive while optimizing overall cluster performance. This leads to better resource utilization and cost efficiency.
Code examples
1apiVersion: kubelet.config.k8s.io/v1beta1
2kind: KubeletConfiguration
3featureGates:
4 MemoryQoS: true
5memoryReservationPolicy: TieredReservation # Options: None (default), TieredReservation
6memoryThrottlingFactor: 0.9 # Optional: default is 0.91apiVersion: kubelet.config.k8s.io/v1beta1
2kind: KubeletConfiguration
3featureGates:
4 MemoryQoS: true
5memoryReservationPolicy: None
6# This is the default$ curl -sk https://localhost:10250/metrics | grep memory_qosWhen NOT to use this
The official docs don't call out specific anti-patterns here. Use your judgment based on your scale and requirements.
Want the complete reference?
Read official docsIndustry-standard certifications built by the people behind Linux and Kubernetes. Earn the CKA — the gold standard Kubernetes administrator cert. OpsCanary readers get 30% off year-round with code OPSCANARY3.
Get CKA certified →Tracing Kueue Admission: Unraveling Workload Mysteries with Headlamp
Understanding how Kueue admission works is crucial for optimizing resource allocation in Kubernetes. With the Kueue plugin for Headlamp, you can trace the admission path of a Workload, revealing insights into its resource requests and conditions. Dive in to learn how to leverage this tool effectively.
Navigating the Shift to cgroup v2 in Kubernetes
Kubernetes is evolving, and so is its resource management with the shift to cgroup v2. Understanding how cgroups manage resources is crucial, especially with features like Memory QoS and the new kubelet defaults. This article dives into what you need to know to leverage these changes effectively.
Mastering Node Swap in Kubernetes: Boosting Workload Resilience
Node swap can be a game changer for your Kubernetes workloads, especially during traffic spikes. By enabling the Linux kernel to page out memory to disk, you can effectively manage memory oversubscription and improve application performance.
Get the daily digest
One email. 5 articles. Every morning.
No spam. Unsubscribe anytime.