kubectl apply

Apply a configuration to a resource by filename or stdin. The resource name must be specified. This resource will be created if it doesn't exist yet. To use 'apply', always create the resource initially with either 'apply' or 'create --save-config'


edit-last-appliedEdit the latest last-applied-configuration annotations of resources from the default editor
set-last-appliedSet the latest last-applied-configuration annotations by setting it to match the contents of a file. This results in the last-applied-configuration being updated as though 'kubectl apply -f<file> ' was run, without updating any other parts of the object
view-last-appliedView the latest last-applied-configuration annotations by type/name or file


-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
--resource-version <arg>If non-empty, the annotation update will only succeed if this is the current resource-version for the object. Only valid when specifying a single resource
--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
--field-selector <arg>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
--localIf true, annotation will NOT contact api-server but run locally
--allSelect all resources, including uninitialized ones, in the namespace of the specified resource types
--allow-missing-template-keysIf 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
-R, --recursiveProcess 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]
--overwriteIf true, allow annotations to be overwritten, otherwise reject annotation updates that overwrite existing annotations
--recordRecord 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
--cascadeIf true, cascade the deletion of the resources managed by this resource (e.g. Pods created by a ReplicationController). Default true
--field-manager <arg>Name of the manager used to track field ownership
--forceIf true, immediately remove resources from API and bypass graceful deletion. Note that immediate deletion of some resources may result in inconsistency or data loss and requires confirmation
--force-conflictsIf true, server-side apply will force the changes against conflicts
--grace-period <INT (seconds)>Period of time in seconds given to the resource to terminate gracefully. Ignored if negative. Set to 1 for immediate shutdown. Can only be set to 0 when --force is true (force deletion)
--openapi-patchIf true, use openapi to calculate diff when the openapi presents and the resource can be found in the openapi spec. Otherwise, fall back to use baked-in types
--overwriteAutomatically resolve conflicts between the modified and live configuration by using values from the modified configuration
--pruneAutomatically delete resource objects, including the uninitialized ones, that do not appear in the configs and are created by either apply or create --save-config. Should be used with either -l or --all
--prune-whitelist <group/version/kind>Overwrite the default whitelist with <group/version/kind> for --prune
--server-sideIf true, apply runs in the server instead of the client
--timeout <INT (Seconds)>The length of time to wait before giving up on a delete, zero means determine a timeout from the size of the object
--validateIf true, use a schema to validate the input before sending it
--waitIf true, wait for resources to be gone before returning. This waits for finalizers