FailedScheduling .../... Insufficient cpu
(Redirected from Insufficient cpu)
Jump to navigation
Jump to search
default 40s Warning FailedScheduling pod/kibana-kibana-654ccb45bd-pbp4r 0/2 nodes are available: 2 Insufficient cpu.
default 40s Warning FailedScheduling pod/opensearch-cluster-master-0 0/3 nodes are available: 3 Insufficient cpu.
0/11 nodes are available: 1 Insufficient cpu, 1 Too many pods, 10 nodes(s) didn't match Pod's node affinity/selector
pod/aws-node-glrc2
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 .../...
Related
kind: Deployment, spec:, containers:, resources: cpu:
- Capacity:
- Allocatable:
- kubectl top
- kubectl get events
- kubectl describe node
- kubectl describe nodes grep cpu
- helm get values
- cluster_autoscaling
- Insufficient memory
default-scheduler
- role.kubernetes.io/controlplane
See also
- FailedScheduling:
Insufficient cpu
,Insufficient memory
,timed out waiting for the condition
,unbound immediate PersistentVolumeClaims
- 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: