Kubernetes taints and tolerations

Taints allow a node to repel a set of pods, in opposite to Node Affinity

• https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/

A taint consists of a key, value, and effect. As an argument here, it is expressed as key=value:effect. The effect must be NoSchedule, PreferNoSchedule or NoExecute.

• kubectl taint

Examples

taints:
   - key: eks.amazonaws.com/compute-type
     value: fargate
     effect: NoSchedule

spec:
  providerID: aws:///us-east-1a/i-085c2fcaaerterq
  taints:
    - key: dedicated
      value: gpuGroup
      effect: NoSchedule

https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/examples/complete/main.tf

     taints = {
       dedicated = {
         key    = "dedicated"
         value  = "gpuGroup"
         effect = "NO_SCHEDULE"
       }
     }

Activities

• Read https://www.mankier.com/1/kubectl-taint
• Read Node taints on managed node groups

Related

• tolerations:
• Node affinity
• aws_eks_node_group
• eks_managed_node_groups
• eks.amazonaws.com/compute-type=fargate:NoSchedule
• NodeRestriction admission plugin
• module.eks_managed_node_group
• Kubernetes labels
• Kubernetes Node Affinity
• kind: NodePool

See also

• Kubernetes taints: kubectl taint
• Kubernetes taints and tolerations, NO_SCHEDULE, NoExecute, module.eks_managed_node_group