Difference between revisions of "FailedScheduling .../... Insufficient cpu"
Jump to navigation
Jump to search
| Line 35: | Line 35: | ||
[[helm get values]] | [[helm get values]] | ||
| + | == See also == | ||
* {{K8s tr}} | * {{K8s tr}} | ||
[[Category:K8s]] | [[Category:K8s]] | ||
Revision as of 07:40, 1 November 2022
default 40s Warning FailedScheduling pod/kibana-kibana-654ccb45bd-pbp4r 0/2 nodes are available: 2 Insufficient cpu.
kubectl describe nodes | grep cpu | grep -v gke cpu: 2 cpu: 1930m cpu 1561m (80%) 1143m (59%) cpu: 2 cpu: 1930m cpu 1533m (79%) 1 (51%)
kubectl describe nodes .../... Allocated resources: (Total limits may be over 100 percent, i.e., overcommitted.) Resource Requests Limits -------- -------- ------ cpu 1561m (80%) 1143m (59%) memory 2713Mi (44%) 3388Mi (56%) ephemeral-storage 0 (0%) 0 (0%) hugepages-1Gi 0 (0%) 0 (0%) hugepages-2Mi 0 (0%) 0 (0%) attachable-volumes-gce-pd 0 0 .../...
kubectl get events kubectl describe node cpu: helm get values
See also
- 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:
