Kubernetes 1.37: Memory QoS graduates to Beta

In Kubernetes v1.37 Memory QoS reached Beta and is enabled by default on kubelets running cgroup v2, yet it writes no settings out of the box. Throttling via memory.high now requires an explicit memoryThrottlingFactor (default null), while memory protection is a separate opt-in via memoryReservationPolicy=TieredReservation.

• Memory QoS is on by default in v1.37 but changes nothing without explicit configuration
• memoryThrottlingFactor now defaults to null instead of 0.9, so throttling is opt-in
• TieredReservation sets memory.min for Guaranteed and memory.low for Burstable pods
• Reservation policy applies node-wide, with no per-pod opt-in or opt-out