Difference between revisions of "Kubernetes taints and tolerations"
Jump to navigation
Jump to search
Tags: Mobile web edit, Mobile edit |
|||
Line 42: | Line 42: | ||
* <code>[[aws eks node group]]</code> | * <code>[[aws eks node group]]</code> | ||
* [[eks_managed_node_groups]] | * [[eks_managed_node_groups]] | ||
− | + | * <code>[[eks.amazonaws.com/compute-type=fargate:NoSchedule]]</code> | |
== See also == | == See also == |
Revision as of 08:54, 9 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
tolerations:
- Node affinity
aws eks node group
- eks_managed_node_groups
eks.amazonaws.com/compute-type=fargate:NoSchedule
See also
Advertising: