Kubernetes 1.37 Stabilizes Metrics API and Adds Rootless Kubelet

Kubernetes 1.37 brings stable metrics monitoring and safer rootless operation to standard clusters, while introducing new tools for AI workload management.
Key points
- Kubernetes 1.37 makes the Metrics API generally available, standardizing health monitoring for auto-scaling tools.
- Rootless Kubelet enters beta, allowing the node agent to run as non-root to reduce container escape risks.
- Resilient watchcache initialization stabilizes large clusters by preventing etcd overload during API server restarts.
The Cloud Native Computing Foundation has released Kubernetes 1.37, a version focused on hardening the platform's core operations. This update moves several experimental features into production-ready status, aiming to make container orchestration more predictable and secure for enterprise environments. According to reporting by infoq.com, the release includes 67 total enhancements, with a specific emphasis on stability and security improvements.
The most significant change for daily operations is the general availability of the Metrics API. Previously in beta, this feature now provides a standardized way to monitor node and pod health. This stability ensures that auto-scaling tools and command-line utilities work consistently across different cluster setups, removing a common source of configuration errors for developers managing dynamic workloads.
Rootless Kubelet Reduces Attack Surface
Security has been a primary driver for the graduation of the Rootless Kubelet to beta status. This feature allows the kubelet, the primary node agent, to run as a non-root user using Linux namespaces. By preventing the agent from having full administrative privileges on the host, the system significantly reduces the potential damage from container escape attacks. This is a critical trade-off for security-conscious organizations, as it limits the blast radius of any compromise.
While this enhances security, running components without root access can introduce complexity in permission management. Operators must ensure that file systems and network interfaces are correctly configured for non-root users. However, the reduction in risk is generally considered worth the operational overhead, especially in multi-tenant environments where isolation is paramount.
Improved Stability for Large Clusters
Kubernetes 1.37 also stabilizes resilient watchcache initialization, a feature designed to prevent control plane outages. In large clusters, restarting the API server previously caused a flood of requests to the etcd database, leading to performance degradation. The new behavior limits these requests and returns graceful error signals when the system is overwhelmed. This prevents cascading failures and keeps the cluster responsive during maintenance or unexpected restarts.
Additionally, pod-to-pod communication now supports native mutual TLS through stable pod certificates. This eliminates the need for external tools to bootstrap secure connections between internal services. For teams building microservices, this simplifies the security architecture by integrating encryption directly into the Kubernetes networking layer, reducing configuration drift and potential vulnerabilities.
New Tools for AI and ML
The release includes new alpha features tailored for artificial intelligence workloads. One such feature is workload-aware scheduling, which allows the scheduler to preempt low-priority tasks to free up resources for high-priority AI jobs. This is particularly relevant for GPU-intensive applications, where resource contention can lead to significant delays. By dynamically managing resource allocation, the system helps optimize the utilization of expensive hardware.
Another alpha feature introduces pod-level checkpoint and restore capabilities. This allows operators to take snapshots of a running container’s memory and process state for debugging or security analysis. While useful for troubleshooting complex AI models, this feature is still experimental and may not be suitable for all production environments. Users should evaluate the stability and resource costs before adopting it for critical workloads.






