OC-ADM-PRUNE-DEPLOYMENTS(1)
π oc adm prune deployments (OC ADM PRUNE(1))
okay so bestie, this page is from the OC ADM PRUNE(1) manual β the Openshift CLI User Manuals fam β and it's literally all about cleaning up your old deployment configs. no cap, it's giving janitor energy but make it glamorous π§Ήβ¨
β¨ NAME β¨
oc adm prune deployments β remove old completed and failed deployment configs ποΈπ
π SYNOPSIS π
oc adm prune deployments [OPTIONS]
π¦ DESCRIPTION π¦
Prune old completed and failed deployment configs. periodt.
But hear me out π β by default, the prune operation performs a dry run making no changes to the deployment configs. So like, it's just gonna tell you what it would do. It's giving window shopping, not actually buying anything ποΈ. You need a --confirm flag for changes to actually be effective. That's the moment it stops playing and starts slaying ππ₯
π OPTIONS π
--confirm=falseβ If true, specify that deployment pruning should proceed. Defaults tofalse, displaying what would be deleted but not actually deleting anything. so like, it's the "do it for real" switch, and it's OFF by default fr fr π--keep-complete=5β Per DeploymentConfig, specify the number of deployments whose status iscompletethat will be preserved whose replica size is 0. the number is 5 unless you say otherwise π--keep-failed=1β Per DeploymentConfig, specify the number of deployments whose status isfailedthat will be preserved whose replica size is 0. just the one, as a treat π₯Ί--keep-younger-than=0β Specify the minimum age of a deployment for it to be considered a candidate for pruning. anything younger gets a pass β³--orphans=falseβ If true, prune all deployments where the associated DeploymentConfig no longer exists, the status iscompleteorfailed, and the replica size is 0. abandoned deployments getting evicted, we love to see it ποΈπ--replica-sets=falseβ EXPERIMENTAL: If true, ReplicaSets will be included in the pruning process. experimental bestie, tread lightly β οΈβ¨
π OPTIONS INHERITED FROM PARENT COMMANDS π
these ones are like, the family traits β they come from the parent command π«Ά
--as=""β Username to impersonate for the operation. User could be a regular user or a service account in a namespace. cosplaying as someone else, iconic π--as-group=[]β Group to impersonate for the operation, this flag can be repeated to specify multiple groups. like, stack 'em as many times as you want π«--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 path is real, don't ask π--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. bestie no ππ this one's genuinely risky, it's not a vibe--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. zero = patience of a saint π§ββοΈ-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. turning warnings into Ls, bold move π
πΈ EXAMPLE πΈ
# Dry run deleting all but the last complete deployment for every deployment config
oc adm prune deployments --keep-complete=1
# To actually perform the prune operation, the confirm flag must be appended
oc adm prune deployments --keep-complete=1 --confirm
see how the second one has --confirm? that's the difference between "haha what if" and "I'm actually doing it" π
π₯
π SEE ALSO π
β HISTORY β
June 2016, Ported from the Kubernetes man-doc generator. vintage β¨
okay that's the whole page bestie, you ate that π and one last cute sign-off: this icon was brought to you by Openshift β the Openshift CLI User Manuals β dated June 2016 ππ¦ go forth and prune responsibly, 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