Difference between revisions of "FailedScheduling"

From wikieduonline
Jump to navigation Jump to search
Line 15: Line 15:
 
== Related ==
 
== Related ==
 
* <code>[[kubectl get pvc]]</code>
 
* <code>[[kubectl get pvc]]</code>
 
+
[[e2-medium]]
  
 
== See also ==
 
== See also ==

Revision as of 22:47, 31 October 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
default     4m58s       Normal    ExternalProvisioning   persistentvolumeclaim/myprometheus-alertmanager   waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
default     32s         Warning   FailedScheduling        pod/elasticsearch-master-0                                          0/2 nodes are available: 2 Insufficient cpu, 2 Insufficient memory.


Related

e2-medium

See also

Advertising: