Difference between revisions of "FailedGetResourceMetric"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
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 == | == Related == | ||
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:
