Taints and tolerations in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding the effect of a NoSchedule taint

What happens when a node has a taint with effect=NoSchedule and a pod does not have a matching toleration?

A The pod will not be scheduled on the node until it has a matching toleration.

B The pod will be scheduled but evicted immediately after starting.

C The pod will be scheduled on the node regardless of the taint.

D The pod will be scheduled only if the node has enough resources.

💡 Hint

Think about what NoSchedule means for pod placement.

A NoSchedule taint prevents pods without matching tolerations from being scheduled on the node. Pods must tolerate the taint to be placed there.

💻 Command Output

intermediate

Output of kubectl describe node with taints

What is the output of kubectl describe node node1 if the node has a taint key=example, value=reserved, effect=NoSchedule?

Kubernetes

kubectl describe node node1

A Taints: example=reserved:NoExecute

B Taints: example=reserved:NoSchedule

C Taints: example:NoSchedule

D Taints: None

💡 Hint

Check the format of taints in the node description.

The taint is shown as key=value:effect. Here, example=reserved:NoSchedule is the correct format.

❓ Configuration

advanced

Correct toleration YAML for NoExecute taint

Which YAML snippet correctly adds a toleration for a NoExecute taint with key special and value true?

A

tolerations:
- key: "special"
  operator: "Equal"
  value: "false"
  effect: "NoExecute"

B

tolerations:
- key: "special"
  operator: "Exists"
  effect: "NoExecute"
  tolerationSeconds: 300

C

tolerations:
- key: "special"
  value: "true"
  effect: "NoSchedule"

D

tolerations:
- key: "special"
  operator: "Equal"
  value: "true"
  effect: "NoExecute"
  tolerationSeconds: 300

💡 Hint

Remember that NoExecute tolerations can specify tolerationSeconds to limit eviction time.

Option D correctly specifies key, operator, value, effect, and tolerationSeconds for a NoExecute taint toleration.

❓ Troubleshoot

advanced

Pod not scheduled despite toleration present

A pod has a toleration for a taint key=zone, value=west, effect=NoSchedule but is still not scheduled on the node with that taint. What could be the reason?

A The toleration's operator is 'Exists' but the taint has a value, so it does not match.

B The pod's toleration effect is 'NoExecute' instead of 'NoSchedule'.

C The toleration's value does not match the taint's value exactly.

D The node is out of CPU resources.

💡 Hint

Check if the toleration's value matches the taint's value exactly.

Tolerations with operator 'Equal' require exact value match. If the values differ, the toleration does not match the taint, so the pod won't schedule.

✅ Best Practice

expert

Choosing the right taint effect for temporary node maintenance

You want to prevent new pods from scheduling on a node temporarily for maintenance but allow existing pods to continue running. Which taint effect should you use?

A NoSchedule

B NoExecute

C PreferNoSchedule

D NoStart

💡 Hint

Consider the difference between preventing scheduling and evicting pods.

NoSchedule prevents new pods from scheduling but does not evict existing pods. NoExecute evicts existing pods. PreferNoSchedule is a soft preference. NoStart is not a valid effect.