cancel
Showing results for 
Search instead for 
Did you mean: 
shcmzzj
Cadet
Cadet
  • 496 Views

Pod can not tolerate to nods - EX280 question

Hello everyone,
I taked the EX280 and didn't pass today.
Which confused me was that the pods can not tolerate to nodes in this exam.
After the task of manual scaling, the pods was stacked at pending status.
After the task of autoscaling, the pods was stacked at pending status.
Even in the tasks that the deploymentconfig has been prepared, the pods was just dead(timeout) there.
So you can not understand what happened there and what to do for the exam.
When I check the events I found the error of the pods like this:  (sorry,but I can't remember all the words)

0/5 nodes are available, 2 nodes taint {node.worker} that can not tolerate, 3 nodes taint {node-role.kubernetes.io/master} that can not tolerate.


What should I do for this? I'm sure that I won't pass the exam if I can't solove the problem.
I have taken the DO280 and I think I didn't see the trouble in this course.
Regards.

Labels (1)
Tags (1)
2 Replies
dgaona77
Cadet
Cadet
  • 468 Views

Re: Pod can not tolerate to nods - EX280 question

Hello shcmzzj

I had exactly the same problem during my exam, which I also didn't pass and I think this "tolerations" contributed.

After revisited the "tolerations and taints" topic, I can see now that, either you need to modify the deploymentConfig to include the correct "tolerations" or remove the taints from the nodes.

Which is the correct? still I don't know.

Reply
Loading...
shcmzzj
Cadet
Cadet
  • 405 Views

Re: Pod can not tolerate to nods - EX280 question

Thank you, dgaona77

I checked the doc of "tolerations and taints" too, and I think both of the ways can resolve this problem.

I also discussed this with my colleague who passed this exam. His choise was modifying all the DeploymentConfig. 

I think I will use the same solution with him in my next exam, though I think that removing the taints should be a faster way.

Reply
Loading...
Join the discussion
You must log in to join this conversation.