label
Update pod ‘foo’ with the label ‘unhealthy’ and the value ‘true’
kubectl label pods foo unhealthy=true
Update pod ‘foo’ with the label ‘status’ and the value ‘unhealthy’, overwriting any existing value
kubectl label --overwrite pods foo status=unhealthy
Update all pods in the namespace
kubectl label pods --all status=unhealthy
Update a pod identified by the type and name in “pod.json”
kubectl label -f pod.json status=unhealthy
Update pod ‘foo’ only if the resource is unchanged from version 1
kubectl label pods foo status=unhealthy --resource-version=1
Update pod ‘foo’ by removing a label named ‘bar’ if it exists # Does not require the —overwrite flag
kubectl label pods foo bar-
Update the labels on a resource.
- A label key and value must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores, up to 63 characters each.
- Optionally, the key can begin with a DNS subdomain prefix and a single ‘/‘, like example.com/my-app.
- If —overwrite is true, then existing labels can be overwritten, otherwise attempting to overwrite a label will result in an error.
- If —resource-version is specified, then updates will use this resource version, otherwise the existing resource-version will be used.
Usage
$ kubectl label [--overwrite] (-f FILENAME | TYPE NAME) KEY_1=VAL_1 ... KEY_N=VAL_N [--resource-version=version]
Flags
Name | Shorthand | Default | Usage |
---|---|---|---|
all | false | Select all resources, including uninitialized ones, in the namespace of the specified resource types | |
all-namespaces | A | false | If true, check the specified action in all namespaces. |
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-label | Name of the manager used to track field ownership. | |
field-selector | Selector (field query) to filter on, supports ‘=’, ‘==’, and ‘!=’.(e.g. —field-selector key1=value1,key2=value2). The server only supports a limited number of field queries per type. | ||
filename | f | [] | Filename, directory, or URL to files identifying the resource to update the labels |
kustomize | k | Process the kustomization directory. This flag can’t be used together with -f or -R. | |
list | false | If true, display the labels for a given resource. | |
local | false | If true, label will NOT contact api-server but run locally. | |
output | o | 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 labels to be overwritten, otherwise reject label updates that overwrite existing labels. | |
record | false | Record current kubectl command in the resource annotation. If set to false, do not record the command. If set to true, record the command. If not set, default to updating the existing annotation value only if one already exists. | |
recursive | R | false | Process the directory used in -f, —filename recursively. Useful when you want to manage related manifests organized within the same directory. |
resource-version | If non-empty, the labels update will only succeed if this is the current resource-version for the object. Only valid when specifying a single resource. | ||
selector | l | Selector (label query) to filter on, not including uninitialized ones, supports ‘=’, ‘==’, and ‘!=’.(e.g. -l key1=value1,key2=value2). | |
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]. |
当前内容版权归 Kubernetes 或其关联方所有,如需对内容或内容相关联开源项目进行关注与资助,请访问 Kubernetes .