Difference between revisions of "FailedScheduling"
Jump to navigation
Jump to search
(Created page with " kubectl get events non-prod 22s Warning FailedScheduling pod/your_elasticsearch-master-1 0/13...") |
|||
| Line 1: | Line 1: | ||
[[kubectl get events]] | [[kubectl get events]] | ||
| − | non-prod 22s Warning FailedScheduling pod/your_elasticsearch-master-1 0/ | + | non-prod 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-simulation}, that the pod didn't tolerate, 7 node(s) had [[volume node affinity conflict]]. |
Revision as of 14:19, 4 July 2022
kubectl get events non-prod 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-simulation}, that the pod didn't tolerate, 7 node(s) had volume node affinity conflict.
See also
kubectl get: [all|componentstatus | pods | apiservices | events|event|nodes|replicaset|services|svc|namespaces|hpa|secret | deployments | serviceaccounts | endpoints | daemonset | networkpolicy],kubectl get -h
Advertising:
