From the course: Debugging Kubernetes

Unlock this course with a free trial

Join today to access over 25,300 courses taught by industry experts.

Debugging missing Pod tolerations and taints

Debugging missing Pod tolerations and taints - Kubernetes Tutorial

From the course: Debugging Kubernetes

Start my 1-month free trial Buy for my team

Debugging missing Pod tolerations and taints

“

- [Instructor] Let's run that describe pods command again. We can do that by typing Control + R, then typing describe pod, and then hitting Enter when we find the command that we ran earlier. In the last video, we talked about something called an untolerated taint. This is another reason why pods might not start. Let's explore this more. Let's run kubectl get pods again. We can see that both pods are still in a Pending state. Now, we know why test-app is in a Pending state, but why is test-app-2 also in a Pending state? Let's run kubectl describe pod test-app-2 to find out. Just like test-app, this pod is failing to be scheduled due to an untolerated taint. However, the taint that's in question here is a little different. Instead of it being something about a control plane, we can see that this debugging.k8s.io/ready taint is untolerated. This taint looks custom-made and is likely our culprit here, but before we fix this, let's learn more about taints and tolerations and why this…

Contents