Difference between revisions of "FailedScheduling .../... Insufficient cpu"
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
[[kubectl describe nodes]] | grep cpu | grep -v gke | [[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 get events]] | [[kubectl get events]] | ||
Revision as of 07:04, 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 get events kubectl describe node cpu:
- 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,CrashLoopBackOff
Advertising:
