Documentation for version v1.10 is no longer actively maintained. The version you are currently viewing is a static snapshot. For up-to-date documentation, see the latest version.
velero completion
Generate completion script
Synopsis
To load completions:
Bash:
$ source <(velero completion bash)
To load completions for each session, execute once:
Linux: $ velero completion bash > /etc/bash_completion.d/velero MacOS: $ velero completion bash > /usr/local/etc/bash_completion.d/velero
Zsh:
If shell completion is not already enabled in your environment you will need
to enable it. You can execute the following once:
$ echo “autoload -U compinit; compinit” » ~/.zshrc
To load completions for each session, execute once:
$ velero completion zsh > “${fpath[1]}/_velero”
You will need to start a new shell for this setup to take effect.
Fish:
$ velero completion fish | source
To load completions for each session, execute once:
$ velero completion fish > ~/.config/fish/completions/velero.fish
velero completion [bash|zsh|fish] [flags]
Options
-h, --help help for completion
Options inherited from parent commands
--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
--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
--log_file string If non-empty, use this log file
--log_file_max_size uint Defines the maximum size a log file can grow to. 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)
--skip_headers If true, avoid header prefixes in the log messages
--skip_log_headers If true, avoid headers when opening log files
--stderrthreshold severity logs at or above this threshold go to stderr (default 2)
-v, --v Level number for the log level verbosity
--vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging
SEE ALSO
- velero - Back up and restore Kubernetes cluster resources.
Getting Started
To help you get started, see the documentation.