OC(1)

💖 OC(1) — okay bestie, let's talk registry 💖

So like, this is the oc registry manual page, and it's giving integrated OpenShift registry management realness. June 2016 energy (we love a retro queen 👑) but the facts are all here, fr fr.

---

🌸 NAME 🌸

oc registry — commands for working with the registry, no cap.

✨ SYNOPSIS ✨

oc registry [OPTIONS]

That's it. That's the vibe. 💅

🎀 DESCRIPTION 🎀

Manage the integrated registry on OpenShift. Lowkey the whole point.

These commands help you work with an integrated OpenShift registry. Like, that's literally what they do bestie, and they ate. 🔥

💜 OPTIONS INHERITED FROM PARENT COMMANDS 💜

Okay so these aren't even this command's options — they're inherited from the parent commands, and there are... a lot of them. But we do not skip. We never skip. Periodt. 🫶

• --as="" — username to impersonate for the operation. User could be a regular user or a service account in a namespace. Yes, you can be someone else, main character energy. 👑
• --as-group=[] — group to impersonate for the operation. This flag can be repeated to specify multiple groups. Stack 'em, bestie.
• --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. Not me being obsessed with that path 😭
• --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. Saving that bandwidth, iconic.
• --insecure-skip-tls-verify=false — if true, the server's certificate will not be checked for validity. ⚠️ This will make your HTTPS connections insecure. Bestie. Do not. Unless you know what you're doing, then do you. 💀
• --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. Strict queen. 🌈
• -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). Pick your fighter. ⭐
• --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. Patience is a virtue, honestly.
• -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. Aggressive but valid. 🦋

---

🔥 SEE ALSO 🔥

Go read these too, bestie, iykyk:

oc(1), oc-registry-info(1), oc-registry-login(1)

🌈 HISTORY 🌈

June 2016 — ported from the Kubernetes man-doc generator. A little throwback moment for the culture. ✨

---

Okay that's the whole thing! No notes, ate and left no crumbs. This page was brought to you by Openshift, part of the Openshift CLI User Manuals, dated June 2016 — and honestly it's still serving. 💅🎀🫶 Go manage that registry, mwah! 🍓🧚💜