OC-ADM-RELEASE(1)

📦
version 4.22.0 · 2 versions
, in nixpkgs unstable

💅 oc adm release — bestie's guide to the OpenShift release pipeline 🎀

okay so real talk, this is the oc adm release command from the OpenShift CLI, and honestly? she's iconic. this is the tool the OpenShift release process itself uses to build images that can update a cluster. main character energy fr fr. ✨

🌸 SYNOPSIS 🌸

oc adm release [OPTIONS]

💖 DESCRIPTION 💖

okay so picture this: oc adm release is the tool that OpenShift release uses to build images that can update a cluster. that's the whole vibe. 👑

the subcommands let you peek at info about releases, do administrative actions to inspect what's actually inside a release, and mirror release content across image registries. it's giving "swiss army knife but make it kubernetes." 🦋

✨ OPTIONS INHERITED FROM PARENT COMMANDS ✨

these are the flags she inherited from her parent commands, and yes, every single one matters. no skipping. 💅

  • --as="" — username to impersonate for the operation. could be a regular user or a service account in a namespace. pick your fighter.
  • --as-group=[] — group to impersonate for the operation. this flag can be repeated to specify multiple groups. stack 'em up 🫶
  • --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. yes that path is real, don't @ me 🙈
  • --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. ⚠️ danger era, proceed with caution
  • --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. periodt.
  • -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. 🔥

🦋 SEE ALSO 🦋

🎀 HISTORY 🎀

June 2016, Ported from the Kubernetes man-doc generator. vintage. 💜

and that's the whole page bestie!! 🌈 source/version is the Openshift CLI User Manuals, dated June 2016, brought to you by Openshift — catch you in the next manpage, mwah 💋✨

📦 where this page comes from