Metrics API reaches stable release, Kubernetes 1.37

Metrics API reaches stable release, Kubernetes 1.37

27 A- A+
In Kubernetes 1.37 the metrics.k8s.io API moves from v1beta1 to the stable (v1) version, strengthening the foundation for reliable pod and node metrics usage and autoscaling.
Metrics API reaches stable release, Kubernetes 1.37 - bimakale.com
08 Eylül 2026 Salı - 14:04 (1 Gün önce) 3 dk okuma

Why moving the Metrics API to a stable version matters

The Kubernetes community, with the v1.37 release, promoted the metrics.k8s.io API out of beta to a stable (v1) level. This step shows that the API will provide the same stability guarantees as other stable components of Kubernetes. Frequently used features such as the kubectl top command and the Horizontal Pod Autoscaler (HPA) rely on this API; therefore, moving to a stable version improves the consistency and reliability of measurement data in production environments.

Core functions and current use cases

The Metrics API reports CPU and memory consumption for each node and pod. This information plays a critical role in two main scenarios:

  • Instant tracking of resource usage: With the kubectl top nodes and kubectl top pods commands, administrators can quickly see the current load of the system.
  • Automatic scaling mechanisms: HPA automatically increases or decreases the number of pods when defined metric thresholds are reached, keeping applications flexible to demand.

In the stable release, the same resource types and fields from v1beta1 are preserved; the only change is that the version label is updated to v1. Developers therefore do not need to relearn the API schema, and version compatibility checks become simpler.

Implications for developers and operations teams

This update directly affects two groups:

Developers: While they continue to use a separate Custom Metrics API to collect application-specific metrics, they can now rely on a stable endpoint for basic CPU and memory measurements. This reduces the risk of metric-accuracy issues when moving from test environments to production in CI/CD pipelines.

Operations teams: Monitoring and alerting systems can consume data coming from metrics.k8s.io with a higher level of confidence. Teams that track SLAs (Service Level Agreements) face a lower likelihood of encountering temporary bugs that are typical of the “beta” phase.

However, the data set provided by the Metrics API only covers basic CPU and memory measurements; teams that want a full monitoring stack still need to integrate additional tools such as Prometheus or Grafana. This makes it clear that the API’s purpose is “fundamental observation” rather than a complete monitoring solution, acting as the “first step.”

Moving to a stable version also simplifies version-compatibility checks within the community. Previously, running components that used v1beta1 alongside v1 in the same cluster could generate incompatibility warnings. Now that the API has a single version, such confusion is avoided and upgrade processes proceed more smoothly.

Teams planning for the future can consider new features built on this stable API. For example, advanced scaling strategies like “Kubernetes Event-driven Autoscaling” require a more reliable metric foundation; the stable API provides the necessary infrastructure.

Finally, this change reinforces the “API maturity” trend in the Kubernetes ecosystem. With each release, critical infrastructure components graduate from beta to stable, accelerating adoption by enterprise customers. The Metrics API becoming stable sends a positive signal regarding security, compliance, and support in large-scale production environments.

Source: Kubernetes Blog

Kaynak: Kubernetes Blog

Alakalı İçerikler

  • Kubernetes
  • Metrics API
  • v1.37
  • otomatik ölçekleme
  • kubectl top
  • kararlı API
  • konteyner izleme
Comments
Add your comment
Kullanıcı
0 character
Bilgisayar Masası
Bilgisayar Masası
53 Article
Other Tags by the Author Show all
Popular Tags Show all
Other content by the author