OC-REGISTRY-INFO(1)

📦
version 4.22.0 · 2 versions
, in nixpkgs unstable

💅 OC REGISTRY INFO — like, the whole manual but make it make sense 🎀

okay bestie, welcome to the oc registry(1) page — specifically the oc registry info corner of the Openshift CLI User Manuals (June 2016 era, vintage ✨). Buckle up, we're getting into it 🦋

🌸 NAME 🌸

oc registry info — the command that prints out info about your integrated registry. that's it, that's the whole vibe 💖

✨ SYNOPSIS ✨

oc registry info [OPTIONS]

🫶 DESCRIPTION 🫶

So basically? This one displays information about the integrated registry. Iconic, lowkey useful.

It exposes the deets about the integrated registry — if one is configured. Like, if there's no registry, there's nothing to spill 🫠

Use --check if you wanna verify your local client can actually access the registry. Vibe check for your connection, fr fr.

Heads up bestie: if the administrator hasn't configured a public host name for the registry, then this command may fail when you run it outside of the server. Not a bug, just the situation 😭

Experimental: this command is under active development and may change without notice. So like… don't build your whole personality around it, it's giving main-character-in-flux 💀

💅 OPTIONS 💅

  • --check=false — attempt to contact the integrated registry. like, actually reach out and see if it answers 🫶
  • --internal=false — only check the internal registry hostname
  • --public=false — only check the public registry hostname
  • -q, --quiet=false — suppress normal output and only print status. minimal queen behavior 👑

👑 OPTIONS INHERITED FROM PARENT COMMANDS 👑

these are the flags you inherit from the parent commands — the family trauma, if you will 💀

  • --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. ⚠️ careful bestie, that's literally the insecure 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
  • --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 🧚

here's the moment you've all been waiting for — the example. copy it exactly, no cap:

# Display information about the integrated registry
oc registry info

🌈 SEE ALSO 🌈

(the trailing comma is part of the original, we don't edit the ancestors 💅)

📜 HISTORY 📜

June 2016, ported from the Kubernetes man-doc generator. vintage ✨ a classic, honestly.

and that's the whole page bestie!! 🎀 this lil number comes to you from Openshift — Openshift CLI User Manuals, dated June 2016. go forth and oc registry info responsibly 🦋💖

📦 where this page comes from