OC-APPLY-VIEW-LAST-APPLIED(1)

πŸ“¦
version 4.22.0 Β· 2 versions
, in nixpkgs unstable

πŸ’– NAME πŸ’–

From the Openshift CLI User Manuals, this is OC APPLY(1) β€” aka oc apply view-last-applied, your bestie for viewing the latest last-applied-configuration annotations of a resource/object. πŸ’…βœ¨

✨ SYNOPSIS ✨

oc apply view-last-applied [OPTIONS]

πŸŽ€ DESCRIPTION πŸŽ€

Okay so: this command views the latest last-applied-configuration annotations by type/name or file. 🫢

The default output gets printed to stdout in YAML format. You can use the -o option to change the output format. Literally that simple, bestie. πŸ’–

🌸 OPTIONS 🌸

  • --all=false β€” Select all resources in the namespace of the specified resource types. πŸ‘‘
  • -f, --filename=[] β€” Filename, directory, or URL to files that contains the last-applied-configuration annotations.
  • -k, --kustomize="" β€” Process the kustomization directory. This flag can't be used together with -f or -R. 🚫
  • -o, --output="yaml" β€” Output format. Must be one of (yaml, json).
  • -R, --recursive=false β€” Process the directory used in -f, --filename recursively. Useful when you want to 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. 🎯

πŸ‘‘ OPTIONS INHERITED FROM PARENT COMMANDS πŸ‘‘

  • --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="/homeless-shelter/.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. ⚠️ Like, actually insecure, bestie β€” not a vibe.
  • --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.
  • --profile="none" β€” Name of profile to capture. One of (none|cpu|heap|goroutine|threadcreate|block|mutex).
  • --profile-output="profile.pprof" β€” Name of the file to write the profile to.
  • --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.
  • --warnings-as-errors=false β€” Treat warnings received from the server as errors and exit with a non-zero exit code. πŸ’€

πŸ¦‹ EXAMPLE πŸ¦‹

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

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

πŸ’œ SEE ALSO πŸ’œ

Go check out oc-apply(1), too, bestie. 🫢

🌈 HISTORY 🌈

June 2016, Ported from the Kubernetes man-doc generator. Periodt. ✨


Stay iconic, bestie β€” this page is brought to you by Openshift / Openshift CLI User Manuals, dated June 2016. πŸ’…πŸŽ€

πŸ“¦ where this page comes from