| Latest revision |
Your text |
| Line 2: |
Line 2: |
| | * https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/#taint-based-evictions | | * https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/#taint-based-evictions |
| | | | |
| − | [[kubectl taint]] [[nodes]] | + | [[kubectl taint]] nodes |
| | | | |
| − | == Example ==
| |
| − | [[kubectl taint]] nodes node1 key1=value1:NoSchedule
| |
| − |
| |
| − |
| |
| − | https://www.mankier.com/1/kubectl-taint
| |
| − | * A taint consists of a key, value, and effect. As an argument here, it is expressed as <code>key=value:effect</code>.
| |
| − | * The key must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores, up to
| |
| − | 253 characters.
| |
| − | * Optionally, the key can begin with a DNS subdomain prefix and a single '/', like example.com/my-app.
| |
| − | * The value is optional. If given, it must begin with a letter or number, and may contain letters, numbers, hyphens,
| |
| − | dots, and underscores, up to 63 characters.
| |
| − | * The effect must be <code>[[NoSchedule]], [[PreferNoSchedule]] or [[NoExecute]]</code>.
| |
| − | * Currently taint can only apply to node.
| |
| − |
| |
| − | Examples:
| |
| − | # Update node 'foo' with a taint with key 'dedicated' and value 'special-user' and effect 'NoSchedule'
| |
| − | # If a taint with that key and effect already exists, its value is replaced as specified
| |
| − | kubectl taint nodes foo dedicated=special-user:NoSchedule
| |
| − |
| |
| − | # Remove from node 'foo' the taint with key 'dedicated' and effect 'NoSchedule' if one exists
| |
| − | kubectl taint nodes foo dedicated:NoSchedule-
| |
| − |
| |
| − | # Remove from node 'foo' all the taints with key 'dedicated'
| |
| − | kubectl taint nodes foo dedicated-
| |
| − |
| |
| − | # Add a taint with key 'dedicated' on nodes having label mylabel=X
| |
| − | kubectl taint node -l myLabel=X dedicated=foo:PreferNoSchedule
| |
| − |
| |
| − | # Add to node 'foo' a taint with key 'bar' and no value
| |
| − | kubectl taint nodes foo bar:NoSchedule
| |
| − |
| |
| − | Options:
| |
| − | --all=false:
| |
| − | Select all nodes in the cluster
| |
| − |
| |
| − | --allow-missing-template-keys=true:
| |
| − | If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to
| |
| − | golang and jsonpath output formats.
| |
| − |
| |
| − | --dry-run='none':
| |
| − | Must be "none", "server", or "client". If client strategy, only print the object that would be sent, without
| |
| − | sending it. If server strategy, submit server-side request without persisting the resource.
| |
| − |
| |
| − | --field-manager='kubectl-taint':
| |
| − | Name of the manager used to track field ownership.
| |
| − |
| |
| − | -o, --output='':
| |
| − | Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath,
| |
| − | jsonpath-as-json, jsonpath-file).
| |
| − |
| |
| − | --overwrite=false:
| |
| − | If true, allow taints to be overwritten, otherwise reject taint updates that overwrite existing taints.
| |
| − |
| |
| − | -l, --selector='':
| |
| − | Selector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l key1=value1,key2=value2). Matching
| |
| − | objects must satisfy all of the specified label constraints.
| |
| − |
| |
| − | --show-managed-fields=false:
| |
| − | If true, keep the managedFields when printing objects in JSON or YAML format.
| |
| − |
| |
| − | --template='':
| |
| − | Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format
| |
| − | is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
| |
| − |
| |
| − | --validate='strict':
| |
| − | Must be one of: strict (or true), warn, ignore (or false). "true" or "strict" will use a schema to validate
| |
| − | the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation
| |
| − | is enabled on the api-server, but will fall back to less reliable client-side validation if not. "warn" will
| |
| − | warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled
| |
| − | on the API server, and behave as "ignore" otherwise. "false" or "ignore" will not perform any schema
| |
| − | validation, silently dropping any unknown or duplicate fields.
| |
| − |
| |
| − | Usage:
| |
| − | kubectl taint NODE NAME KEY_1=VAL_1:TAINT_EFFECT_1 ... KEY_N=VAL_N:TAINT_EFFECT_N [options]
| |
| − |
| |
| − | </pre>
| |
| − |
| |
| − | == Related ==
| |
| − | * <code>[[tolerations:]]</code>
| |
| | | | |
| | == See also == | | == See also == |
| − | * {{kubectl taint}} | + | * {{kubectl}} |
| − | * {{kubectl nodes}}
| |
| | | | |
| | [[Category:Kubernetes]] | | [[Category:Kubernetes]] |
