KUBERNETES(1)(kubernetes)

👑 KUBERNETES(1) — the kubectl apply view-last-applied glow-up 💅

okay bestie, welcome to section 1 of the kubernetes manual, where we're gonna talk about one (1) extremely specific little command. it's not the flashiest, but it's giving forensic investigator energy and honestly? obsessed. ✨

---

✨ NAME ✨

kubectl apply view-last-applied — peek at the latest last-applied-configuration annotations of a resource/object 👀

---

🌸 SYNOPSIS 🌸

kubectl apply view-last-applied [OPTIONS]

---

🦋 DESCRIPTION 🦋

So basically: this lets you view the latest last-applied-configuration annotations, and you can grab them either by type/name or by file. That's it, that's the whole vibe.

By default the output just gets printed to stdout in YAML format. Don't like YAML? That's valid. Use the -o option to switch the output format up. 💖

---

🎀 OPTIONS 🎀

• --all=false — select all the resources in the namespace of whatever resource types you specified.
• -f, --filename=[] — filename, directory, or URL to files that contain the last-applied-configuration annotations.
• -k, --kustomize="" — process the kustomization directory. ⚠️ this flag can't be used together with -f or -R, so don't try it, she will not cooperate.
• -o, --output="yaml" — output format. has to be one of (yaml, json). no rogue formats, bestie.
• -R, --recursive=false — process the directory used in -f, --filename recursively. super useful when you wanna manage related manifests organized within the same directory.
• -l, --selector="" — selector (label query) to filter on, supports =, ==, !=, in, notin. (e.g. -l key1=value1,key2=value2,key3 in (value3)). matching objects must satisfy all of the specified label constraints, no halfsies.

---

💜 OPTIONS INHERITED FROM PARENT COMMANDS 💜

these are the ones your command got from its parent, like genetic material but for flags:

• --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, so like, be so serious about this one.
• --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. 😤 no notes.

---

🌈 EXAMPLE 🌈

the main character moments, ft. real commands you can literally copy:

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

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

---

🫶 SEE ALSO 🫶

• kubectl-apply(1)

---

📜 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! 💀 iconic origin story ngl.

---

and that's the whole page, bestie. this came from the Manuals collection, User section, manual name KUBERNETES(1)(kubernetes) — go forth and view those last-applied configs, you ate. 🌟💖