Library HPA objects are not scaling and kubectl top in that namespace also returns no metrics. What does this combination most strongly suggest?
Select an answer to reveal the explanation.
Short Explanation
If both top and HPA are blind, the metrics hose is kinked—usually metrics-server or the metrics path—not a NetworkPolicy magic switch.
Full Explanation
HorizontalPodAutoscalers that target CPU or memory require metrics. When kubectl top also fails or returns no data for the namespace, the shared root cause is typically missing or unhealthy metrics collection (commonly metrics-server). NetworkPolicies, PV reclaim policies, and node Ready alone do not replace a working metrics pipeline for HPA.