oadm-prune-builds man page
oadm prune builds — Remove old completed and failed builds
oadm prune builds [Options]
Prune old completed and failed builds
By default, the prune operation performs a dry run making no changes to internal registry. A --confirm flag is needed for changes to be effective.
Specify that build pruning should proceed. Defaults to false, displaying what would be deleted but not actually deleting anything.
Per BuildConfig, specify the number of builds whose status is complete that will be preserved.
Per BuildConfig, specify the number of builds whose status is failed, error, or cancelled that will be preserved.
Specify the minimum age of a Build for it to be considered a candidate for pruning.
Prune all builds whose associated BuildConfig no longer exists and whose status is complete, failed, error, or cancelled.
Options Inherited from Parent Commands
DEPRECATED: The API version to use when talking to the server
Username to impersonate for the operation
Path to a cert. file for the certificate authority
Path to a client certificate file for TLS
Path to a client key file for TLS
The name of the kubeconfig cluster to use
Path to the config file to use for CLI requests.
The name of the kubeconfig context to use
The Google Cloud Platform Service Account JSON Key to use for authentication.
If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure
Maximum number of seconds between log flushes
Require server version to match client version
- -n, --namespace=""
If present, the namespace scope for this CLI request
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.
The address and port of the Kubernetes API server
Bearer token for authentication to the API server
The name of the kubeconfig user to use
June 2016, Ported from the Kubernetes man-doc generator