Kubernetes v1.37 Promotes Metrics API to General Availability
The Kubernetes Metrics API has graduated to General Availability in version 1.37, providing formal stability and long-term compatibility guarantees for resource monitoring.
The Kubernetes community has promoted the Metrics API to v1 status in the v1.37 release. This API serves as the core interface for retrieving CPU and memory usage metrics from Nodes and Pods, powering essential operational tools such as the kubectl top command and the Horizontal Pod Autoscaler. While the API has been in a beta state since Kubernetes v1.8, this graduation establishes formal stability guarantees for enterprise operators.
Primary source
Open Kubernetes Blog ↗This article summarizes the source. Check the original for full details and conditions.
Comparison
| Aspect | Before / Alternative | After / This |
|---|---|---|
| API Version | metrics.k8s.io/v1beta1 | metrics.k8s.io/v1 |
| Stability & Support | Beta-level stability with potential deprecation risks | GA-level backwards compatibility and long-term support |
| Resource Schema | Standard Node/Pod CPU and memory fields | Identical fields and schemas as the beta version |
Action Checklist
- Identify usages of the v1beta1 Metrics API in manifests and automation scripts Check custom dashboards, scripting tools, and Kubernetes operator configurations.
- Update API references in configuration files from v1beta1 to v1 Verify that your cluster is running Kubernetes v1.37 or later before applying changes.
- Verify Horizontal Pod Autoscaler definitions continue to function with the v1 API Ensure autoscaling policies are correctly interpreting resource metrics under the new API version.