✳flâneur — a map of the web's best reading

Taints and Tolerations, Node Affinity, and Node Selector — Explained | by Ilan Spiegel | saas-infra | Medium

medium.com · 1,113 words · saved by 1 readers

Taint and affinity in Kubernetes are two mechanisms that allow users to specify how pods should be scheduled on nodes in a cluster. Node selectors are another mechanism that allows users to specify which nodes a pod should be scheduled on. In this article, we will explain the difference between taint, affinity, and node selector in Kubernetes and how they can be used to control pod scheduling in a cluster. Taint is a feature in Kubernetes that allows users to mark a node as "tainted" with a specific key and value. Pods that do not have toleration for the taint will not be scheduled on the tainted node. Taint can be used to mark nodes as unavailable for certain pods, for example, if the node is undergoing maintenance or has a specific hardware or software configuration that is unsuitable for certain workloads. To taint a node, use the kubectl taint command. For example, to taint a node with key "disktype" and value "ssd", use the following command: To tolerate a taint, you can specify t

Taints and Tolerations, Node Affinity, and Node Selector — Explained Ilan Spiegel 5 min read · Jan 1, 2023 -- 2 Listen Share Taint and affinity in Kubernetes are two mechanisms that allow users to specify how pods should be scheduled on nodes in a cluster. Node selectors are another mechanism that allows users to specify which nodes a pod should be scheduled on. In this article, we will explain the difference between taint, affinity, and node selector in Kubernetes and how they can be used to control pod scheduling in a cluster. Taint Press enter or click to view image in full size Different t

Explore this link on the map →

saved by

related reading