KUBERNETES(1)(kubernetes)

💖 KUBERNETES(1)(kubernetes) — the kubectl apply edit-last-applied glow-up 💖

okay bestie, welcome to the kubernetes manual, section 1 🫶 this whole page was written by Eric Paris back in Jan 2015, and we're about to make it make sense. no cap.

---

✨ NAME ✨

kubectl apply edit-last-applied — Edit latest last-applied-configuration annotations of a resource/object 💅

like… it edits the latest last-applied-configuration annotations. yes the name is a little unhinged. we love her anyway.

---

🌸 SYNOPSIS 🌸

kubectl apply edit-last-applied [OPTIONS]

---

🦋 DESCRIPTION 🦋

So here's the vibe: this command opens up the latest last-applied-configuration annotations of your resources in your default editor and lets you just… edit them. raw. unfiltered. no yaml babysitter. 😌

The edit-last-applied command lets you directly edit any API resource you can retrieve via the command-line tools. It'll pop open the editor defined by your KUBE_EDITOR or EDITOR environment variables, or fall back to vi on Linux / notepad on Windows if you didn't set anything. ✨

You can edit multiple objects, but heads up — changes are applied one at a time. The command accepts file names and command-line arguments, but the files you point to must be previously saved versions of resources. it's giving "bring your own receipt" energy, fr fr.

The default format is YAML. Wanna edit in JSON? specify "-o json". iconic behavior. 💖

The flag --windows-line-endings can be used to force Windows line endings, otherwise the default for your operating system will be used. (your OS decides. she's the main character here.)

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. no skipping this step bestie, the server does not care about your feelings.

---

🎀 OPTIONS 🎀

• --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.
• --field-manager="kubectl-client-side-apply" — Name of the manager used to track field ownership. (yes that's the default. yes it's a whole sentence. she's got range.)
• -f, --filename=[] — Filename, directory, or URL to files to use to edit the resource
• -k, --kustomize="" — Process the kustomization directory. This flag can't be used together with -f or -R. pick a lane 💅
• -o, --output="" — Output format. One of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). that's the whole menu, order it exactly like this.
• --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.
• -R, --recursive=false — Process the directory used in -f, --filename recursively. Useful when you want to manage related manifests organized within the same directory. 🌈
• --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. 👑
• --windows-line-endings=false — Defaults to the line ending native to your platform.

---

💜 OPTIONS INHERITED FROM PARENT COMMANDS 💜

these are the family traits bestie, they came from the parent command and they're all here, every single one:

• --as="" — Username to impersonate for the operation. User could be a regular user or a service account in a namespace.
• --as-group=[] — Group to impersonate for the operation, this flag can be repeated to specify multiple groups.
• --as-uid="" — UID to impersonate for the operation.
• --as-user-extra=[] — User extras to impersonate for the operation, this flag can be repeated to specify multiple values for the same key.
• --cache-dir="/home/username/.kube/cache" — Default cache directory
• --certificate-authority="" — Path to a cert file for the certificate authority
• --client-certificate="" — Path to a client certificate file for TLS
• --client-key="" — Path to a client key file for TLS
• --cluster="" — The name of the kubeconfig cluster to use
• --context="" — The name of the kubeconfig context to use
• --disable-compression=false — If true, opt-out of response compression for all requests to the server
• --insecure-skip-tls-verify=false — If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure ⚠️ (dangerous, we said it, dramatic but true)
• --kubeconfig="" — Path to the kubeconfig file to use for CLI requests.
• --kuberc="" — Path to the kuberc file to use for preferences. This can be disabled by exporting KUBECTL_KUBERC=false feature gate or turning off the feature KUBERC=off.
• --match-server-version=false — Require server version to match client version
• -n, --namespace="" — If present, the namespace scope for this CLI request
• --password="" — Password for basic authentication to the API server
• --profile="none" — Name of profile to capture. One of (none|cpu|heap|goroutine|threadcreate|block|mutex|trace)
• --profile-output="profile.pprof" — Name of the file to write the profile to
• --proxy-url="" — Proxy URL to use for requests to the API server
• --request-timeout="0" — The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests.
• -s, --server="" — The address and port of the Kubernetes API server
• --tls-server-name="" — Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used
• --token="" — Bearer token for authentication to the API server
• --user="" — The name of the kubeconfig user to use
• --username="" — Username for basic authentication to the API server
• --version=false — --version, --version=raw prints version information and quits; --version=vX.Y.Z... sets the reported version
• --warnings-as-errors=false — Treat warnings received from the server as errors and exit with a non-zero exit code

---

🌟 EXAMPLE 🌟

literally just copy these, they ate:

# Edit the last-applied-configuration annotations by type/name in YAML
kubectl apply edit-last-applied deployment/nginx

# Edit the last-applied-configuration annotations by file in JSON
kubectl apply edit-last-applied -f deploy.yaml -o json

---

🔥 SEE ALSO 🔥

• kubectl-apply(1),

go read that one next, iykyk 🫶

---

🧚 HISTORY 🧚

January 2015, Originally compiled by Eric Paris (eparis at redhat dot com) based on the kubernetes source material, but hopefully they have been automatically generated since! 😭 (the "hopefully" is doing so much work here, honestly iconic.)

---

k bye bestie — this page lives in the Manuals manual, User section, titled KUBERNETES(1)(kubernetes). mwah 💋 go edit some annotations. ✨🌸💅