OC-ADM-PRUNE-BUILDS(1)
πΈ OC ADM PRUNE BUILDS(1) πΈ
okay bestie, welcome to the OpenShift CLI User Manuals section of your life π
this one lives in oc adm prune and it's literally all about clearing out your old builds. buckle up π
β¨ NAME β¨
oc adm prune builds β remove old completed and failed builds ποΈβ¨
π¦ SYNOPSIS π¦
oc adm prune builds [OPTIONS]
π DESCRIPTION π
Prune old completed and failed builds. that's it, that's the whole vibe π§Ή
By default, the prune operation performs a dry run making no changes to internal registry β so like, it's window shopping only π you need a --confirm flag for changes to actually be effective. no confirm, no deleting. periodt.
β οΈ ngl, this is the part everyone skips: without --confirm nothing gets deleted, fr fr. it just tells you what would go.
β OPTIONS β
--confirm=falseβ if true, specify that build pruning should proceed. defaults tofalse, which means it displays what would be deleted but does not actually delete anything π--keep-complete=5β per BuildConfig, specify the number of builds whose status is complete that will be preserved π--keep-failed=1β per BuildConfig, specify the number of builds whose status is failed, error, or cancelled that will be preserved π«Ά--keep-younger-than=0β specify the minimum age of a Build for it to be considered a candidate for pruning β³--orphans=falseβ if true, prune all builds whose associated BuildConfig no longer exists and whose status is complete, failed, error, or cancelled π»
π OPTIONS INHERITED FROM PARENT COMMANDS π
these are the hand-me-downs from the parent command, and yes there are a lot of them, but we're listing every single one because we don't do half measures here π
--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 π (like, actually insecure, be careful)--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.--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 iconic demo, bestie β dry run first, then confirm π
# Dry run deleting older completed and failed builds and also including
# all builds whose associated build config no longer exists
oc adm prune builds --orphans
# To actually perform the prune operation, the confirm flag must be appended
oc adm prune builds --orphans --confirm
see how the second one has --confirm? that's the difference between "hmm interesting" and "it's gone" πβ¨
π SEE ALSO π
π HISTORY π
June 2016, Ported from the Kubernetes man-doc generator π
and that's the whole page, bestie π«Ά you ate that π
Openshift β Openshift CLI User Manuals β June 2016 πΈ (yes the source/version and date go here, cute sign-off style, mwah π)
π¦ 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