Member-only story

Kubernetes Taints and Toleration

Ishan Liyanage
5 min readFeb 14, 2021

Lets discuss about the POD to Node relationship and how you can restrict what pods are placed on what nodes. The concept of taints and tolerations can be a bit confusing at first.

Lets take the example and using a analogy of a bug approaching a person.

To prevent the bug from landing on the person, we sprayed the person with a repellent spray or a taint as we will call it. The bug is intolerant to the smell.

The taint applied on the person will throw the bug off. However there could be other bugs that are tolerant to the smell and so the taint does not really affect. So other bug will end up landing on the person.

So there are two things that decide if a bug can land on a person.

  1. The taint on the person.
  2. The bugs toleration level to that particular taint.

Lets map this scenario in to Kubernetes. The person is a node and the bugs are the pods. Taints and tolerations are used to set restrictions on what pods can be scheduled on the nodes.

Lets start with simple cluster with three worker nodes.

Create an account to read the full story.

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

Ishan Liyanage
Ishan Liyanage

Written by Ishan Liyanage

Passionate Technical Lead, Senior Software Developer and free and open source software advocate. Based in Singapore.

Responses (1)

Write a response