Difference between revisions of "FailedScheduling"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | [[kubectl get events]] | + | [[kubectl get events -A]] |
your-namespace 22s Warning [[FailedScheduling]] pod/your_elasticsearch-master-1 0/8 nodes are available: 1 [[Insufficient cpu]], 1 node(s) had taint {risk: etl}, that the pod didn't tolerate, 1 node(s) were unschedulable, 3 node(s) had [[taint]] {NAME: run-your-command}, that the pod didn't tolerate, 7 node(s) had [[volume node affinity conflict]]. | your-namespace 22s Warning [[FailedScheduling]] pod/your_elasticsearch-master-1 0/8 nodes are available: 1 [[Insufficient cpu]], 1 node(s) had taint {risk: etl}, that the pod didn't tolerate, 1 node(s) were unschedulable, 3 node(s) had [[taint]] {NAME: run-your-command}, that the pod didn't tolerate, 7 node(s) had [[volume node affinity conflict]]. | ||
| Line 6: | Line 6: | ||
your-namespace 2m16s Warning FailedScheduling pod/your-elasticsearch-master-1 | your-namespace 2m16s Warning FailedScheduling pod/your-elasticsearch-master-1 | ||
0/13 nodes are available: 1 Insufficient cpu, 1 node(s) had taint {risk: etl}, that the pod didn't tolerate, 3 node(s) had taint {Name: run-your-command}, that the pod didn't tolerate, 4 node(s) had volume node affinity conflict, 4 node(s) [[were unschedulable]]. | 0/13 nodes are available: 1 Insufficient cpu, 1 node(s) had taint {risk: etl}, that the pod didn't tolerate, 3 node(s) had taint {Name: run-your-command}, that the pod didn't tolerate, 4 node(s) had volume node affinity conflict, 4 node(s) [[were unschedulable]]. | ||
| + | |||
| + | default 8m51s Warning FailedScheduling pod/myprometheus-alertmanager-5967d4ff85-5glkh running PreBind plugin "VolumeBinding": binding volumes: timed out waiting for the condition | ||
== See also == | == See also == | ||
Revision as of 05:53, 26 September 2022
kubectl get events -A your-namespace 22s Warning FailedScheduling pod/your_elasticsearch-master-1 0/8 nodes are available: 1 Insufficient cpu, 1 node(s) had taint {risk: etl}, that the pod didn't tolerate, 1 node(s) were unschedulable, 3 node(s) had taint {NAME: run-your-command}, that the pod didn't tolerate, 7 node(s) had volume node affinity conflict.
your-namespace 2m16s Warning FailedScheduling pod/your-elasticsearch-master-1
0/13 nodes are available: 1 Insufficient cpu, 1 node(s) had taint {risk: etl}, that the pod didn't tolerate, 3 node(s) had taint {Name: run-your-command}, that the pod didn't tolerate, 4 node(s) had volume node affinity conflict, 4 node(s) were unschedulable.
default 8m51s Warning FailedScheduling pod/myprometheus-alertmanager-5967d4ff85-5glkh running PreBind plugin "VolumeBinding": binding volumes: timed out waiting for the condition
See also
- Kubernetes events, Kubernetes node events:
[ Normal | Warning ],kubectl events, kubectl get events:BackOff,FailedMount, FailedAttachVolume, TaintManagerEviction, InvalidDiskCapacity,FailedScheduling, kubectl describe events, Unhealthy,conditions:, UpdatedLoadBalancer, BackoffLimitExceeded kubectl get: [all|componentstatus | pods | apiservices | events|event|nodes|replicaset|services|svc|namespaces|hpa|secret | deployments | serviceaccounts | endpoints | daemonset | networkpolicy],kubectl get -h
Advertising:
