Use Kubernetes Metrics API v1 without breaking Prometheus or HPA

Separate the stable API, v1beta1 autoscaling compatibility, and historical alerting before touching dashboards.

Kubernetes v1.37 makes Metrics API stable. This guide shows how to validate v1 with metrics-server, keep HPA compatibility, and avoid confusing it with Prometheus, cAdvisor, or kube-state-metrics.

Created: August 30, 2026

Published: August 30, 2026

Estimated time40 min

LevelIntermediate

Before you startA Kubernetes cluster with metrics-server or a compatible metrics.k8s.io provider.

PlatformsLinux

WhatsApp X LinkedIn

Linux

Local workflow with kubectl, curl against the aggregated API, Prometheus, and promtool.

kubectlcurlpromtool

Check Metrics API v1 and v1beta1 availability

kubectl get apiservice v1.metrics.k8s.io v1beta1.metrics.k8s.io -o wide

Compare resource view and Prometheus source

kubectl top pods -n shop && curl -s localhost:9090/api/v1/query --data-urlencode query="container_memory_working_set_bytes{namespace="shop"}"

Also available inUsar Kubernetes Metrics API v1 sin romper Prometheus ni HPA

Content locked

This guide requires both steps before full content is available.

○Click “Like” on this guide.
○Share on WhatsApp, X, LinkedIn, or copy the link.

Access is automatically unlocked as soon as both steps are completed.