--allow-missing-template-keys | 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 <Strategy> | 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 |
-f, --filename <File> | Filename, directory, or URL to files identifying the resource |
-k, --kustomize <Kustomize Dir> | Process the kustomization directory. This flag can't be used together with -f or -R |
-o, --output <Output Format> | Output format. One of: json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-file |
--local | If true, annotation will NOT contact api-server but run locally |
-R, --recursive | Process the directory used in -f, --filename recursively. Useful when you want to manage related manifests organized within the same directory |
-l, --selector <arg> | Selector (label query) to filter on, not including uninitialized ones, supports '=', '==', and '!='.(e.g. -l key1=value1,key2=value2) |
--template <arg> | 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] |
--record | 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 |
--all | Select all resources, including uninitialized ones, in the namespace of the specified resource types |
-c, --containers <arg> | The names of containers in the selected pod templates to change, all containers are selected by default - may use wildcards |
--limits <arg> | The resource requirement requests for this container. For example, 'cpu=100m,memory=256Mi'. Note that server side components may assign requests depending on the server configuration, such as limit ranges |
--requests <arg> | The resource requirement requests for this container. For example, 'cpu=100m,memory=256Mi'. Note that server side components may assign requests depending on the server configuration, such as limit ranges |