Difference between revisions of "Kubernetes taints and tolerations"
Jump to navigation
Jump to search
Line 8: | Line 8: | ||
* 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 [[NoSchedule]], [[PreferNoSchedule]] or [[NoExecute]]. | ||
+ | |||
+ | |||
+ | == Example == | ||
+ | taints: | ||
+ | - key: [[eks.amazonaws.com/compute-type]] | ||
+ | value: fargate | ||
+ | effect: NoSchedule | ||
== Activities == | == Activities == |
Revision as of 20:09, 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
Activities
Related
See also
Advertising: