Forum archive › Kubernetes & Helm Charts

Error: node(s) had untolerated taint .preemption: 0/3 nodes are available:

Read-only archive. These discussions are from Tracston's earlier technical forum and are kept online because the answers are still useful. New replies are closed. Need help with something like this? Talk to us.

Question 30 Jun 2022

Problem

User tries to schedule ingress / pod / svc on cluster and gets the following error

3 node(s) had untolerated taint {node.kubernetes.io/unreachable: }. preemption: 0/4 nodes are available: 4 Preemption is not helpful for scheduling.

Solution

Remove the taints on the master so that you can schedule pods on it.

kubectl taint nodes –all node-role.kubernetes.io/master-
# Or from specific Node
kubectl taint nodes <NODE NAME> dedicated=special-user:NoSchedule

# You can add taint to control plane to disable pod scheduling 
kubectl taint nodes <NODE NAME> node-role.kubernetes.io/control-plane:NoSchedule-

#Or remove taint from control plane
kubectl taint nodes –all node-role.kubernetes.io/control-plane- node-role.kubernetes.io/master-

Need this fixed properly?

We do this for a living.

Kubernetes, DevOps and platform engineering, delivered in days — not another weekend lost to a stack trace.

Start a project →