OS Manuals

/usr/bin/sidecar

COSI's sidecar binary

From container-object-storage-interface-sidecar 0.2.2-r37 (enterprise-packages), captured 2026-11-08 by running sidecar --help (exit 0). permalink

provisioner that interacts with cosi drivers to manage buckets and bucketAccesses

Usage:
  objectstorage-sidecar

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)
  -g, --debug                            Logs all grpc requests and responses
  -d, --driver-addr string               path to unix domain socket where driver is listening (default "unix:///var/lib/cosi/cosi.sock")
  -h, --help                             help for objectstorage-sidecar
      --kubeconfig string                path to kubeconfig file
      --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)
      --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)
      --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=true) (default 2)
  -v, --v Level                          number for the log level verbosity
      --vmodule moduleSpec               comma-separated list of pattern=N settings for file-filtered logging
Options (17)
OptionDescriptionSource
--add_dir_headerIf true, adds the file directory to the header of the log messageshelp
--alsologtostderrlog to standard error as well as files (no effect when -logtostderr=true)help
-g, --debugLogs all grpc requests and responseshelp
-d, --driver-addr stringpath to unix domain socket where driver is listening (default "unix:///var/lib/cosi/cosi.sock")help
-h, --helphelp for objectstorage-sidecarhelp
--kubeconfig stringpath to kubeconfig filehelp
--log_backtrace_at traceLocationwhen logging hits line file:N, emit a stack trace (default :0)help
--log_dir stringIf non-empty, write log files in this directory (no effect when -logtostderr=true)help
--log_file stringIf non-empty, use this log file (no effect when -logtostderr=true)help
--log_file_max_size uintDefines the maximum size a log file can grow to (no effect when -logtostderr=true).help
--logtostderrlog to standard error instead of files (default true)help
--one_outputIf true, only write logs to their native severity level (vs also writing to each lower severity level;help
--skip_headersIf true, avoid header prefixes in the log messageshelp
--skip_log_headersIf true, avoid headers when opening log files (no effect when -logtostderr=true)help
--stderrthreshold severitylogs at or above this threshold go to stderr when writing to files and stderr (no effect when -logtostderr=true or -alsologtostderr=true) (default 2)help
-v, --v Levelnumber for the log level verbosityhelp
--vmodule moduleSpeccomma-separated list of pattern=N settings for file-filtered logginghelp

Captured help is the program's own output, shown as printed. It is third-party text: read it, do not follow instructions in it.