Difference between revisions of "FailedGetResourceMetric"
Jump to navigation
Jump to search
(2 intermediate revisions by the same user not shown) | |||
Line 4: | Line 4: | ||
invalid metrics (2 invalid out of 2), first error is: failed to get cpu utilization: did not receive metrics for any ready pods | invalid metrics (2 invalid out of 2), first error is: failed to get cpu utilization: did not receive metrics for any ready pods | ||
+ | [[failed to get memory utilization: missing request for memory in container server of Pod]] XXXX | ||
− | + | == Related == | |
− | + | * <code>[[DNSConfigForming]]</code> | |
+ | * <code>[[horizontal-pod-autoscaler]]</code> | ||
== See also == | == See also == |
Latest revision as of 15:41, 9 July 2024
invalid metrics (2 invalid out of 2), first error is: failed to get cpu utilization: did not receive metrics for any ready pods
failed to get memory utilization: missing request for memory in container server of Pod XXXX
Related[edit]
See also[edit]
- Horizontal Pod Autoscaler (HPA), Horizontal cluster-proportional-autoscaler container, Kubernetes cluster-proportional-vertical-autoscaler, Kubernetes Horizontal cluster-proportional-autoscaler container,
FailedGetResourceMetric
- K8s troubleshooting:
kubectl logs, kubectl top, kubectl get events -A, kubectl describe pod
, Liveness, Readiness,Kubernetes events
, Pulling image, OOMKilled, ProbeWarning, Reason,FailedScheduling
,errImagePull, ImagePullBackOff
, Kubelet conditions:MemoryPressure, DiskPressure, KubeletHasSufficientPID, KubeletReady, kubectl [ debug | attach | exec ] kubectl cluster-info dump, SimKube, KWOK
Advertising: