Difference between revisions of "Kubernetes taints and tolerations"
Jump to navigation
Jump to search
Tags: Mobile web edit, Mobile edit |
Tags: Mobile web edit, Mobile edit |
||
| Line 7: | Line 7: | ||
* A taint consists of a key, value, and effect. As an argument here, it is expressed as <code>[[key=value:effect]]</code> | * A taint consists of a key, value, and effect. As an argument here, it is expressed as <code>[[key=value:effect]]</code> | ||
| − | * The effect must be [[NoSchedule]], [[PreferNoSchedule]] or [[NoExecute]]. | + | * The effect must be <code>[[NoSchedule]], [[PreferNoSchedule]] or [[NoExecute]].</code> |
Revision as of 08:01, 7 March 2023
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.
Contents
Example
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
Related
See also
Advertising:
