Discussions
Issue with DaemonSet Pods Not Running in Kubernetes Cluster
4 months ago by Ronak
I have an issue with my daemonset (ds) in my production cluster, where the pods never run. I have 27 nodes but not all of them have the pods for my ds. The specific nodes where the ds pods are not running are:
- gke-oat-1087418191068-p0-gke-euw1-cast-pool-2bfd6cfa
- gke-oat-1087418191068-p0-gke-euw1-cast-pool-46d5d0ff
- gke-oat-1087418191068-p0-gke-euw1-cast-pool-dad613da
I'm receiving the following warning message:
FailedScheduling: 0/25 nodes are available: 1 Insufficient cpu. preemption: 0/25 nodes are available: 25 No preemption victims found for incoming pod.
Additionally, when I try to add the priority class, I receive another warning message:
FailedCreate: Error creating: insufficient quota to match these scopes: [{PriorityClass In [system-node-critical system-cluster-critical]}]
Any suggestions on how to resolve this?