apply

Apply resources from a directory containing kustomization.yaml - e.g. dir/kustomization.yaml

Apply the JSON passed into stdin to a pod

  1. cat pod.json | kubectl apply -f -

Note: —prune is still in Alpha # Apply the configuration in manifest.yaml that matches label app=nginx and delete all other resources that are not in the file and match label app=nginx

    Apply a configuration to a resource by file name 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’.

    JSON and YAML formats are accepted.

    Alpha Disclaimer: the —prune functionality is not yet complete. Do not use unless you are aware of what the current state is. See https://issues.k8s.io/34274.

    $ kubectl apply (-f FILENAME | -k DIRECTORY)

    Flags

    Edit the last-applied-configuration annotations by file in JSON

    1. kubectl apply edit-last-applied -f deploy.yaml -o json

    Edit the latest last-applied-configuration annotations of resources from the default editor.

    The edit-last-applied command allows you to directly edit any API resource you can retrieve via the command-line tools. It will open the editor defined by your KUBE_EDITOR, or EDITOR environment variables, or fall back to ‘vi’ for Linux or ‘notepad’ for Windows. You can edit multiple objects, although changes are applied one at a time. The command accepts file names as well as command-line arguments, although the files you point to must be previously saved versions of resources.

    The default format is YAML. To edit in JSON, specify “-o json”.

    The flag —windows-line-endings can be used to force Windows line endings, otherwise the default for your operating system will be used.

    In the event an error occurs while updating, a temporary file will be created on disk that contains your unapplied changes. The most common error when updating a resource is another editor changing the resource on the server. When this occurs, you will have to apply your changes to the newer version of the resource, or update your temporary saved copy to include the latest resource version.

    $ kubectl apply edit-last-applied (RESOURCE/NAME | -f FILENAME)

    Flags

    Set the last-applied-configuration of a resource to match the contents of a file

    1. kubectl apply set-last-applied -f deploy.yaml

    Set the last-applied-configuration of a resource to match the contents of a file; will create the annotation if it does not already exist

    Set 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 ‘ was run, without updating any other parts of the object.

    $ kubectl apply set-last-applied -f FILENAME

    Flags

    View the last-applied-configuration annotations by type/name in YAML

    1. kubectl apply view-last-applied deployment/nginx

    View the last-applied-configuration annotations by file in JSON

    1. kubectl apply view-last-applied -f deploy.yaml -o json

    View the latest last-applied-configuration annotations by type/name or file.

    The default output will be printed to stdout in YAML format. You can use the -o option to change the output format.

    Flags