Kubernetes taints and tolerations
Jump to navigation
Jump to search
Taints allow a node to repel a set of pods, in opposite to Node Affinity
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 describe nodes | grep Taints
Contents
Examples[edit]
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[edit]
Errors[edit]
Related[edit]
tolerations:- Node affinity
aws_eks_node_groupeks_managed_node_groupseks.amazonaws.com/compute-type=fargate:NoSchedule- NodeRestriction admission plugin
- module.eks_managed_node_group
- Kubernetes labels
- Kubernetes Node Affinity
- kind: NodePool
See also[edit]
Advertising: