Difference between revisions of "Kubernetes taints and tolerations"
Jump to navigation
Jump to search
Line 15: | Line 15: | ||
value: [[fargate]] | value: [[fargate]] | ||
effect: NoSchedule | effect: NoSchedule | ||
+ | |||
+ | |||
+ | |||
+ | [[spec:]] | ||
+ | [[providerID]]: aws:///us-east-1a/i-085c2fcaf46d41c3f | ||
+ | taints: | ||
+ | - key: dedicated | ||
+ | value: [[gpuGroup]] | ||
+ | effect: NoSchedule | ||
== Activities == | == Activities == |
Revision as of 20:21, 1 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-085c2fcaf46d41c3f taints: - key: dedicated value: gpuGroup effect: NoSchedule
Activities
Related
See also
Advertising: