What is Taint in Kubernetes: Explanation and Usage

In Kubernetes, a taint is a property applied to a node that prevents pods from being scheduled on it unless the pod has a matching toleration. Taints help control which pods can run on specific nodes by repelling pods that do not tolerate the taint.

How It Works

Think of a taint as a "Do Not Disturb" sign on a Kubernetes node. When a node has a taint, it tells the system to avoid placing pods there unless those pods explicitly say they can handle the taint. This is done by adding a toleration to the pod.

This mechanism helps manage workloads by controlling pod placement. For example, if a node is reserved for special tasks or has limited resources, taints prevent regular pods from using it accidentally. Pods without matching tolerations are "repelled" from tainted nodes, ensuring only suitable pods run there.

Example

This example shows how to add a taint to a node and how a pod can tolerate it to be scheduled on that node.

bash and yaml

kubectl taint nodes node1 key=value:NoSchedule

apiVersion: v1
kind: Pod
metadata:
  name: tolerant-pod
spec:
  containers:
  - name: nginx
    image: nginx
  tolerations:
  - key: "key"
    operator: "Equal"
    value: "value"
    effect: "NoSchedule"

Output

node/node1 tainted

Pod 'tolerant-pod' will be scheduled on node1 because it tolerates the taint.

When to Use

Use taints when you want to control which pods can run on certain nodes. For example:

• Reserve nodes for high-priority or special workloads.
• Prevent pods from running on nodes with limited resources or special hardware.
• Isolate nodes for testing or maintenance by repelling normal pods.

This helps keep your cluster organized and ensures pods run where they are best suited.

Key Points

• Taints repel pods from nodes unless pods have matching tolerations.
• They help control pod scheduling and node usage.
• Taints have a key, value, and effect (like NoSchedule).
• Pods must declare tolerations to be scheduled on tainted nodes.

Key Takeaways

Taints prevent pods from scheduling on nodes unless pods tolerate them.

Use taints to reserve or isolate nodes for specific workloads.

Pods need matching tolerations to run on tainted nodes.

Taints have effects like NoSchedule to control pod placement.