Difference between revisions of "Velero client"
Jump to navigation
Jump to search
(Created page with "{{lc}} == See also == * {{Velero}} Category:K8s") |
|||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
{{lc}} | {{lc}} | ||
+ | [[velero client config]] | ||
+ | |||
+ | Velero client related commands | ||
+ | |||
+ | Usage: | ||
+ | velero client [command] | ||
+ | |||
+ | Available Commands: | ||
+ | config Get and set client configuration file values | ||
+ | |||
+ | Flags: | ||
+ | -h, --help help for client | ||
+ | |||
+ | 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 | ||
+ | |||
+ | Use "velero client [command] --help" for more information about a command. | ||
+ | |||
== See also == | == See also == |
Latest revision as of 09:58, 24 January 2024
velero client config
Velero client related commands Usage: velero client [command] Available Commands: config Get and set client configuration file values Flags: -h, --help help for client 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 Use "velero client [command] --help" for more information about a command.
See also[edit]
- 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
Advertising: