What is Taint & Toleration?
Kubernetes mechanism to repel pods from nodes unless they explicitly tolerate the taint.
Taints are applied to nodes to repel pods from being scheduled on them. Tolerations are applied to pods to allow them to be scheduled on tainted nodes. Together they implement node dedication: 'only GPU workloads on GPU nodes', 'no general workloads on spot nodes'. Effects: NoSchedule (don't schedule), PreferNoSchedule (prefer not), NoExecute (evict existing + don't schedule). This lets you reserve specialized hardware or separate workloads by type.
More Kubernetes Terms
Admission Controller
A Kubernetes plugin that intercepts API requests before objects are persisted.
Auto Scaling
Automatically adjusting the number of compute resources based on demand.
ClusterIP
The default Kubernetes Service type that exposes a service on an internal cluster IP.
ConfigMap
A Kubernetes object for storing non-sensitive configuration data as key-value pairs.
Controller Manager
Kubernetes control plane component running control loops to maintain desired state.
CoreDNS
The default DNS server in Kubernetes clusters for service discovery.
Test your knowledge of Taint & Toleration and 130 other DevOps concepts