good evening/morning dear members of the forum
i’m newbie in the Kubernetes world and unfortunately for nearly a month i’m fighting to make it work
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Warning FailedScheduling 53m default-scheduler 0/1 nodes are available: 1 node(s) had taint {key: value}, that the pod didn’t tolerate.
thank you so much guys for all the help and collaboration
Can you give us some context on when this problem occurs? Any info you have could help
@Philipe_Rhome
Read https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/
You have a kubernetes cluster with just one node and that one node has a taint on it. This means your pod won’t be scheduled on that node as long as it has this taint, and since you do not have any other nodes in your cluster your pod can’t be scheduled at all.
- You need to find out what taints you have on this node
then you need to either
- remove the taint from the node
or
- add a toleration to the YAML of the pod you want the schedule to allow it to run on this node