Solution

Mon, 01 Jan 0001 00:00:00 +0000

Test

Try to create a pod:

kubectl run ghost --image=ghost:4

Verify it is running:

$ kubectl get po
NAME READY STATUS RESTARTS AGE
ghost 0/1 Pending 0 10s

There is definitely something wrong as the pod remains in pending status.

$ kubectl describe po ghost
...
Events:
 Type Reason Age From Message
 ---- ------ ---- ---- -------
 Warning FailedScheduling 4s (x2 over 72s) default-scheduler 0/3 nodes are available: 3 node(s) had taint {app: secure}, that the pod didn't tolerate.

It seems the 3 nodes have a taint that prevents the pod from being scheduled. We can see there are 2 taints on the master:

Challenge 6 on Exoscale Academy

Solution