Velero backup delete

velero backup delete --help
Delete backups 

Usage:
 velero backup delete [NAMES] [flags]

Examples:
  # Delete a backup named "backup-1".
  velero backup delete backup-1

  # Delete a backup named "backup-1" without prompting for confirmation.
  velero backup delete backup-1 --confirm

  # Delete backups named "backup-1" and "backup-2".
  velero backup delete backup-1 backup-2

  # Delete all backups triggered by schedule "schedule-1".
  velero backup delete --selector velero.io/schedule-name=schedule-1

  # Delete all backups.
  velero backup delete --all

Flags:
     --all                      Delete all backups
     --confirm                  Confirm deletion
 -h, --help                     help for delete
 -l, --selector labelSelector   Delete all backups matching this label selector. (default <none>)

Global Flags:
     --add_dir_header                   If true, adds the file directory to the header of the log messages
     --alsologtostderr                  log to standard error as well as files (no effect when -logtostderr=true)
     --colorized optionalBool           Show colored output in TTY. Overrides 'colorized' value from $HOME/.config/velero/config.json 
if present. Enabled by default
     --features stringArray             Comma-separated list of features to enable for this Velero process. Combines with values from 
$HOME/.config/velero/config.json if present
     --kubeconfig string                Path to the kubeconfig file to use to talk to the Kubernetes apiserver. If unset, try the 
environment variable KUBECONFIG, as well as in-cluster configuration
     --kubecontext string               The context to use to talk to the Kubernetes apiserver. If unset defaults to whatever your 
current-context is (kubectl config current-context)
     --log_backtrace_at traceLocation   when logging hits line file:N, emit a stack trace (default :0)
     --log_dir string                   If non-empty, write log files in this directory (no effect when -logtostderr=true)
     --log_file string                  If non-empty, use this log file (no effect when -logtostderr=true)
     --log_file_max_size uint           Defines the maximum size a log file can grow to (no effect when -logtostderr=true). Unit is 
megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
     --logtostderr                      log to standard error instead of files (default true)
 -n, --namespace string                 The namespace in which Velero should operate (default "velero")
     --one_output                       If true, only write logs to their native severity level (vs also writing to each lower severity 
level; no effect when -logtostderr=true)
     --s2a_enable_appengine_dialer      If true, opportunistically use AppEngine-specific dialer to call S2A.
     --s2a_timeout duration             Timeout enforced on the connection to the S2A service for handshake. (default 3s)
     --skip_headers                     If true, avoid header prefixes in the log messages
     --skip_log_headers                 If true, avoid headers when opening log files (no effect when -logtostderr=true)
     --stderrthreshold severity         logs at or above this threshold go to stderr when writing to files and stderr (no effect when - logtostderr=true or -alsologtostderr=false) (default 2)
 -v, --v Level                          number for the log level verbosity
     --vmodule moduleSpec               comma-separated list of pattern=N settings for file-filtered logging

velero delete

See also

• velero backup [ create | describe | logs | download | get | delete ]
• Velero: [backup | backup-location | bug | client | completion | create | debug | delete | get | describe | help | install] kubectl kots velero | plugin | repo | restore | schedule | uninstall], helm install velero, --help, Velero: Cluster migration