Toleration
A Kubernetes toleration is Pod scheduling configuration that permits placement on a node with a matching taint without guaranteeing placement there.
Google Anthos in Action
A Kubernetes toleration is pod scheduling configuration that permits a pod to be placed on a node with a matching taint.
- How it is used
- Controls whether a Pod may be placed on a tainted node during workload scheduling.
- How deep it goes
- Explains taint effects and matching Pod configuration through manifests, without detailing the scheduler’s matching internals.
- Examples
- Uses a GPU-only node with a NoSchedule taint, matching Pod toleration, node selector, and placement output.
- What you can do after
- Operate/configure it with kubectl and a Pod manifest to permit intended workloads on tainted nodes and verify placement.
Kubernetes for Developers
A Kubernetes toleration is Pod scheduling configuration that permits placement on nodes with a matching taint without guaranteeing that placement.
- How it is used
- Uses Pod configuration to permit selected workloads onto tainted nodes for hardware access, Spot capacity, or workload separation.
- How deep it goes
- Explains matching taints, NoSchedule behavior, selectors, and scheduling diagnosis, while stopping short of exhaustive taint-effect reference.
- Examples
- Demonstrates Spot nodes, GPU nodes, grouped Deployments, DaemonSets, and Pending Pods caused by unmatched taints.
- What you can do after
- Operate/configure Kubernetes workloads with tolerations and diagnose taint-related scheduling failures.
Acing the Certified Kubernetes Administrator Exam, Second Edition
A toleration is a Kubernetes pod scheduling specification that permits placement on a node with a matching taint.
- How it is used
- Controls whether pods may run on tainted nodes during cluster administration and CKA scheduling tasks.
- How deep it goes
- Explains taint matching through keys, optional values, effects, YAML inspection, and kubectl verification, without detailing scheduler internals.
- Examples
- Uses the control-plane NoSchedule taint, CoreDNS toleration output, and a generated nginx pod manifest for practical verification.
- What you can do after
- Operate/configure pods with tolerations and verify their placement using kubectl node and pod output.
Read how Acing the Certified Kubernetes Administrator Exam, Second Edition explains toleration →
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 it is used
- Uses tolerations to let DaemonSet pods reach tainted control-plane nodes and provide services on every cluster node.
- 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 you can do after
- Configure a DaemonSet pod with Exists to tolerate all taints and schedule across control-plane and worker nodes.
Read how Kubernetes in Action, Second Edition explains 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.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.