OC-ADM-PRUNE-AUTH(1)
π oc adm prune auth β the glow-up your cluster's role references deserve π
okay so this is a page from the OpenShift CLI User Manuals (oc adm prune family, June 2016 energy) and bestie, it's about cleaning up dangling references. Let's get into it β¨
πΈ NAME πΈ
oc adm prune auth β literally removes references to the roles, clusterroles, users, and groups you point at. bye-bye stale refs π
β¨ SYNOPSIS β¨
oc adm prune auth [OPTIONS]
that's it. that's the whole vibe check. options go after π
π¦ DESCRIPTION π¦
so what it does: it removes references to the roles, clusterroles, users, and groups you specify. that's the whole main character job.
and the plot twist? Other types are ignored. not invited to the party. not even on the list. π
π OPTIONS π
--all=falseβ prune all the roles in the namespace. yes, all of them. no cap. lowkey a big move π-f,--filename=[]β filename, directory, or URL to files containing the resource to delete. give it a path, give it a link, it'll handle it π«Ά-k,--kustomize=""β process the kustomization directory. important: this flag can't be used together with-for-R. it's giving "pick one, bestie" π-R,--recursive=falseβ process the directory you passed in-f,--filenamerecursively. super useful when you want to manage related manifests organized within the same directory. so, same folder energy β¨-l,--selector=""β selector (label query) to filter on. labels are how you find your people π
π OPTIONS INHERITED FROM PARENT COMMANDS π
these come from the parent command, they're like the family traits. not this command's own, but they ride along π§
--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 for a sec π--as-group=[]β group to impersonate for the operation. this flag can be repeated to specify multiple groups. collect them all π--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's the literal default path, don't come for 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. uncompressed and unbothered π--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. that's not a vibe, that's a warning π¨--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 exportingKUBECTL_KUBERC=falsefeature gate or turning off the featureKUBERC=off. two ways to say no π--match-server-version=falseβ require server version to match client version. be picky about it β¨-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. zero = infinite patience fr fr β³-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. strict mode activated π€
π SEE ALSO π
oc-adm-prune(1)β the parent, the origin story π«Ά
π HISTORY π
June 2016, ported from the Kubernetes man-doc generator. vintage. iconic. a classic π
so yeah bestie, that's the whole page β prune those auth references, don't mix -k with -f/-R, and please don't casually turn off TLS verification unless you really mean it πβ¨
β signed off with love from the OpenShift CLI User Manuals, Openshift edition, June 2016 era π¦
π¦ 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