Kubernetes / Deployments, Scheduling & Batch Workloads
Find why a HorizontalPodAutoscaler cannot obtain its metrics
An HPA can exist without a functioning metrics pipeline or compatible target. Inspect its conditions before manually scaling repeatedly.
Environment and inputs: Kubernetes · kubectl with supported client/server versions and delegated RBAC. Examples use namespace app unless noted. Check context, namespace, APIs and provider support first.
Start with this check
Confirm the environment and replace sample objects, namespaces, images, paths and hosts with approved targets. Share only relevant, sanitized output. Follow the workload owner’s process for changes.
kubectl -n app describe hpa webRead the result
The output includes desired/current behavior, metric status and events. A missing metrics API differs from a target lacking required resource requests.
Resolve and verify
Repair the demonstrated metrics-server, adapter or workload configuration and verify fresh metric values. Observe scaling under representative controlled load.
Before changing production
Do not remove autoscaling safeguards or assume a single current value validates the whole metrics path.