Error in log when trying to create a kubernetes cluster saying 1 node(s) had taints that the pod didn't tolerate.

0 votes

I am trying to create a kube cluster and my pods were in the pending state. When I tried looking at the logs, I found something fishy

There was an error saying 

1 node(s) had taints that the pod didn't tolerate.

What does that mean and how do I get rid of it?

Jan 11 in Kubernetes by Clapton

1 answer to this question.

Your answer

Your name to display (optional):
Privacy: Your email address will only be used for sending these notifications.
0 votes

You get this error when your pod is not being able to schedule to your worker nodes. This could be coz of various reasons - pods not ready, nodes not ready, not sufficient memory etc. 

I think here your nodes haven't joined the cluster yet, there is no way it is going to deploy a pod on a worker node and hence the error.

You can remove the taint using this command but chose this is your last option as it's not a good practice. What it will do is, it'll start deploying pods on your master instead of your worker nodes which we do not want. 

kubectl taint nodes--all
answered Jan 11 by Yesha
But that won't work right? Pods cannot be executed on the master right? Theoretically, its impossible right?

Related Questions In Kubernetes

0 votes
1 answer
0 votes
1 answer

permissions related to AWS ECR

if you add allowContainerRegistry: true, kops will add those permissions ...READ MORE

answered Oct 9, 2018 in Kubernetes by Kalgi
• 36,420 points
0 votes
3 answers

Error while joining cluster with node

Hi Kalgi after following above steps it ...READ MORE

answered Jan 17 in Others by anonymous
0 votes
3 answers
0 votes
1 answer

© 2018 Brain4ce Education Solutions Pvt. Ltd. All rights Reserved.
"PMP®","PMI®", "PMI-ACP®" and "PMBOK®" are registered marks of the Project Management Institute, Inc. MongoDB®, Mongo and the leaf logo are the registered trademarks of MongoDB, Inc.