Three days of releases, one briefing.

What happened:
- Kubernetes v1.37 shipped a set of features across storage and node-resource management: bind mount options and emptyDir permission modes for hardening container storage (Alpha) [1], Pod-Level Resource Managers graduating to Beta [2], and Memory QoS graduating to Beta and enabled by default [3].

What is new:
- Bind mount options (`bindMountOptions`, e.g. noexec, nosuid) and emptyDir permission `mode` (including sticky bit 01777) were introduced as Alpha features (`VolumeBindMountOptions` and `EmptyDirVolumeMode` gates) to address long-standing security gaps flagged in issues #48912 and #119627 [1].
- Pod-Level Resource Managers reached Beta (disabled by default), letting Kubelet's Topology, CPU, and Memory Managers use pod-level resource declarations for hybrid NUMA allocation, and added `cpu_ids`/`memory` fields to the PodResources gRPC API [2].
- Memory QoS reached Beta and is now enabled by default; the default `memoryThrottlingFactor` changed from 0.9 to null so upgrading does not change existing runtime behavior; a known limitation is that `memoryReservationPolicy` applies node-wide with no per-pod opt-in, tracked in kubernetes/kubernetes#140246 [3].

Where the sources disagree:
- No overlapping claims, numbers, names, or dates are given differently across the pages; each source covers a distinct feature area, so there are no direct disagreements to report.

All three numbered sources [1][2][3] were read; none were unreadable.

Sources
  [1] Kubernetes v1.37: Hardening Container Storage with Bind Mount Options and EmptyDir Permissions  https://kubernetes.io/blog/2026/09/16/kubernetes-v1-37-hardening-container-storage/
  [2] Kubernetes v1.37: Pod-Level Resource Managers graduated to Beta  https://kubernetes.io/blog/2026/09/15/kubernetes-v1-37-pod-level-resource-managers-beta/
  [3] Kubernetes v1.37: Memory QoS Graduates to Beta  https://kubernetes.io/blog/2026/09/14/kubernetes-v1-37-memory-qos-graduates-to-beta/