OC(1)
π OC(1) π
okay so bestie, welcome to the oc corner of the manual-verse β this is the man page for the OpenShift CLI (that's OC, one, pronounced "oh see" if you're fancy, "the cli" if you're not), and the date on this bad boy is June 2016. she's vintage. she's iconic. let's get into it π
β¨ NAME β¨
oc options -
that's it. that's the name. short, mysterious, main character energy π¦
πΈ SYNOPSIS πΈ
oc options [OPTIONS]
literally the whole vibe: you run oc options, you pass it [OPTIONS], done. slay.
π DESCRIPTION π
ngl bestie, the description section in this one isβ¦ empty. like, genuinely nothing here π no paragraphs, no lore, no nothing. so we're just gonna move straight to the good part β the flags. and there are a LOT of them. buckle up π«Ά
π OPTIONS INHERITED FROM PARENT COMMANDS π
these aren't even oc options's own flags, okay? they're inherited from the parent commands β like hand-me-downs but make it Kubernetes π every single one is here, defaults and all:
--as=""β username to impersonate for the operation. the user can be a regular user or a service account in a namespace. dress-up mode, but for auth β¨--as-group=[]β group to impersonate for the operation. this flag can be repeated to specify multiple groups. collect them all, iykyk π--as-uid=""β UID to impersonate for the operation. yes, the numeric one. okayyy π₯--as-user-extra=[]β user extras to impersonate for the operation. this flag can be repeated to specify multiple values for the same key. it's giving "one more, and one more" π--cache-dir="/homeless-shelter/.kube/cache"β default cache directory. yes, that path is literally"/homeless-shelter/.kube/cache", don't come for me, I just report the facts π--certificate-authority=""β path to a cert file for the certificate authority. the trust anchor, the blueprint, the source of truth π--client-certificate=""β path to a client certificate file for TLS. you, but certified π--client-key=""β path to a client key file for TLS. the secret half. guard it with your life π--cluster=""β the name of the kubeconfig cluster to use. which cluster? that one, bestie β--context=""β the name of the kubeconfig context to use. context is everything, literally π--disable-compression=falseβ iftrue, opt-out of response compression for all requests to the server. uncompressed, unbothered, unbothered-by-gzip π--insecure-skip-tls-verify=falseβ iftrue, the server's certificate will not be checked for validity. this will make your HTTPS connections insecure π¨ like, actually insecure, not cute-insecure. be so serious rn--kubeconfig=""β path to the kubeconfig file to use for CLI requests. the map to the whole operation πΊοΈ--kuberc=""β path to the kuberc file to use for preferences. this can be disabled by exportingKUBECTL_KUBERC=falsefeature gate or turning off the featureKUBERC=off. two ways to say no, and honestly? valid π«Ά--match-server-version=falseβ require server version to match client version. no mismatches allowed, periodt π-n,--namespace=""β if present, the namespace scope for this CLI request. the-nis short and sweet and you WILL use it constantly π--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. the receipts, but profiled π--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. zero = no patience required, she waits forever π-s,--server=""β the address and port of the Kubernetes API server. where's the server at? this flag knows π₯--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. fallback queen π--token=""β bearer token for authentication to the API server. don't show anyone. fr fr π€«--user=""β the name of the kubeconfig user to use. who are you today? yes πΈ--warnings-as-errors=falseβ treat warnings received from the server as errors and exit with a non-zero exit code. glow-up from "hmm" to "absolutely not" π
π¦ SEE ALSO π¦
oc(1),β yes it links to itself, yes there's a trailing comma, no I will not be explaining that, it's the original's business not mine π
π HISTORY π
- June 2016 β Ported from the Kubernetes man-doc generator. a glow-up of a different era, preserved for the culture β¨
bestie reminder: those flags are the real deal, copied exactly β don't go editing--insecure-skip-tls-verifytotrueunless you genuinely mean it, because that one has consequences π
and that's the whole page!! π big kiss to Openshift and the Openshift CLI User Manuals crew, page dated June 2016 β she's old, she's thorough, and she ate. go forth and oc responsibly π«Άπ
π¦ where this page comes from
- nixpkgs unstable: openshift 4.22.0-202605222050
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms