Toleration

As explained in Kubernetes in Action, Second Edition

A toleration is a pod scheduling specification that permits a pod to be scheduled onto a node with a matching taint.

How Kubernetes in Action, Second Edition covers it

How deep it goes

Defines matching taints and demonstrates Exists, but defers detailed taint effects and toleration matching rules.

Examples

Uses the kube-proxy DaemonSet manifest and its Exists toleration as the concrete scheduling example.

What it assumes

Assumes basic pods and DaemonSets, while introducing taints and tolerations as the scheduling mechanism.

What you can do after

Configure a DaemonSet pod with Exists to tolerate all taints and schedule across control-plane and worker nodes.

How it connects

Connects tolerations with taints, pod scheduling, DaemonSets, control-plane nodes, and kube-proxy.

liveBookmanning.com

Read Kubernetes in Action, Second Edition on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Google Anthos in ActionA Kubernetes toleration is pod scheduling configuration that permits a pod to be placed on a node with a matching taint.
• 

  liveBookmanning.com
  Kubernetes for DevelopersA Kubernetes toleration is Pod scheduling configuration that permits placement on nodes with a matching taint without guaranteeing that placement.
• 

  liveBookmanning.com
  Acing the Certified Kubernetes Administrator Exam, Second EditionA toleration is a Kubernetes pod scheduling specification that permits placement on a node with a matching taint.

Compare how 4 books explain toleration →

Related concepts

• taintaddresses · A Kubernetes taint is a node attribute that repels Pods lacking a matching toleration according to the taint’s effect.
• workload separationused by · Workload separation is the isolation of distinct computational workloads to limit interference from resource use or failures in one workload.
• podconfigures · A Kubernetes Pod is the smallest deployable unit in Kubernetes, grouping one or more co-located containers that share networking and other resources.
• admission controllerconfigured by · A Kubernetes admission controller intercepts API requests after authentication and authorization, validating or mutating them before they are persisted.
• affinityused by · Node affinity is a Kubernetes scheduling constraint that requires or prefers placing a pod on nodes whose labels match specified expressions.

This explainer was generated by Manning's knowledge graph from the text of Kubernetes in Action, Second Edition. The section links point to the parts of the book it draws on.