Difference between revisions of "FailedGetResourceMetric"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| + | |||
| + | |||
| + | invalid metrics (2 invalid out of 2), first error is: failed to get cpu utilization: did not receive metrics for any ready pods | ||
| Line 5: | Line 8: | ||
[[horizontal-pod-autoscaler]] | [[horizontal-pod-autoscaler]] | ||
| + | |||
| + | {{HPA}} | ||
{{K8s tr}} | {{K8s tr}} | ||
Revision as of 07:49, 14 September 2023
invalid metrics (2 invalid out of 2), first error is: failed to get cpu utilization: did not receive metrics for any ready pods
DNSConfigForming horizontal-pod-autoscaler
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:
