Usage of /usr/bin/keda-admission-webhooks: --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) --alsologtostderrthreshold severity logs at or above this threshold go to stderr when -alsologtostderr=true (no effect when -logtostderr=true) --cache-miss-to-direct-client If true, on cache misses the webhook will call the direct client to fetch the object --cert-dir string Webhook certificates dir to use. Defaults to /certs (default "/certs") --ginkgo.always-emit-ginkgo-writer [DEPRECATED] - use -v instead, or one of Ginkgo's machine-readable report formats to get GinkgoWriter output for passing specs. --ginkgo.debug [DEPRECATED] --ginkgo.dry-run If set, ginkgo will walk the test hierarchy without actually running anything. Best paired with -v. --ginkgo.dryRun [DEPRECATED] use --ginkgo.dry-run instead --ginkgo.fail-fast If set, ginkgo will stop running a test suite after a failure occurs. --ginkgo.fail-on-empty If set, ginkgo will mark the test suite as failed if no specs are run. --ginkgo.fail-on-pending If set, ginkgo will mark the test suite as failed if any specs are pending. --ginkgo.failFast [DEPRECATED] use --ginkgo.fail-fast instead --ginkgo.failOnPending [DEPRECATED] use --ginkgo.fail-on-pending instead --ginkgo.fd If set, emits RSpec-style 'format documentation' output instead of Ginkgo's default output. --fd is exclusive: it overrides -p/-procs and -randomize-all, forcing specs to run serially in declaration order, since fd's hierarchical output can't be rendered sensibly when specs are parallelized or randomized. --ginkgo.flake-attempts int Make up to this many attempts to run each spec. If any of the attempts succeed, the suite will not be failed. --ginkgo.flakeAttempts int [DEPRECATED] use --ginkgo.flake-attempts instead --ginkgo.focus stringSliceVar If set, ginkgo will only run specs that match this regular expression. Can be specified multiple times, values are ORed. --ginkgo.focus-file stringSliceVar If set, ginkgo will only run specs in matching files. Can be specified multiple times, values are ORed. --ginkgo.force-newlines If set, default reporter will ensure a newline appears after each test. --ginkgo.github-output If set, default reporter prints easier to manage output in Github Actions. --ginkgo.gojson-report string If set, Ginkgo will generate a Go JSON-formatted test report at the specified location. --ginkgo.grace-period duration When interrupted, Ginkgo will wait for GracePeriod for the current running node to exit before moving on to the next one. (default 30s) --ginkgo.json-report string If set, Ginkgo will generate a JSON-formatted test report at the specified location. --ginkgo.junit-report string If set, Ginkgo will generate a conformant junit test report in the specified file. --ginkgo.label-filter string If set, ginkgo will only run specs with labels that match the label-filter. The passed-in expression can include boolean operations (!, &&, ||, ','), groupings via '()', and regular expressions '/regexp/'. e.g. '(cat || dog) && !fruit' --ginkgo.no-color If set, suppress color output in default reporter. You can also set the environment variable GINKGO_NO_COLOR=TRUE --ginkgo.noColor [DEPRECATED] use --ginkgo.no-color instead --ginkgo.noisyPendings [DEPRECATED] --ginkgo.noisySkippings [DEPRECATED] --ginkgo.output-interceptor-mode string If set, ginkgo will use the specified output interception strategy when running in parallel. Defaults to dup on unix and swap on windows. --ginkgo.parallel.host string The address for the server that will synchronize the processes. --ginkgo.parallel.process int This worker process's (one-indexed) process number. For running specs in parallel. (default 1) --ginkgo.parallel.total int The total number of worker processes. For running specs in parallel. (default 1) --ginkgo.poll-progress-after duration Emit node progress reports periodically if node hasn't completed after this duration. (default 0s) --ginkgo.poll-progress-interval duration The rate at which to emit node progress reports after poll-progress-after has elapsed. (default 0s) --ginkgo.progress [DEPRECATED] . The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck. --ginkgo.randomize-all If set, ginkgo will randomize all specs together. By default, ginkgo only randomizes the top level Describe, Context and When containers. --ginkgo.randomizeAllSpecs [DEPRECATED] use --ginkgo.randomize-all instead --ginkgo.regexScansFilePath [DEPRECATED] --ginkgo.reportFile string [DEPRECATED] use --ginkgo.junit-report instead --ginkgo.seed int The seed used to randomize the spec suite. (default 1794235919) --ginkgo.sem-ver-filter string If set, ginkgo will only run specs with semantic version constraints that are satisfied by the provided version. e.g. '2.1.0' --ginkgo.show-node-events If set, default reporter prints node > Enter and < Exit events when specs fail --ginkgo.silence-skips If set, default reporter will not print out skipped tests. --ginkgo.skip stringSliceVar If set, ginkgo will only run specs that do not match this regular expression. Can be specified multiple times, values are ORed. --ginkgo.skip-file stringSliceVar If set, ginkgo will skip specs in matching files. Can be specified multiple times, values are ORed. --ginkgo.sleep-on-failure duration If set, ginkgo will pause for this duration after a spec fails - before its teardown (AfterEach/JustAfterEach/DeferCleanup) runs - so you can inspect the live system. Press ^C to end the pause early and proceed to cleanup. Serial only: cannot be combined with -p/--procs. (default 0s) --ginkgo.slow-spec-threshold duration [DEPRECATED] --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck. (default 0s) --ginkgo.slowSpecThreshold float [DEPRECATED] use --slow-spec-threshold instead and pass in a duration string (e.g. '5s', not '5.0') --ginkgo.source-root stringSliceVar The location to look for source code when generating progress reports. You can pass multiple --source-root flags. --ginkgo.succinct If set, default reporter prints out a very succinct report --ginkgo.teamcity-report string If set, Ginkgo will generate a Teamcity-formatted test report at the specified location. --ginkgo.timeout duration Test suite fails if it does not complete within the specified timeout. (default 1h0m0s) --ginkgo.trace If set, default reporter prints out the full stack trace when a failure occurs --ginkgo.v If set, emits more output including GinkgoWriter contents. --ginkgo.vv If set, emits with maximal verbosity - includes skipped and pending tests. --health-probe-bind-address string The address the probe endpoint binds to. (default ":8081") --kube-api-burst int Set the burst for throttling requests sent to the apiserver (default 30) --kube-api-qps float32 Set the QPS rate for throttling requests sent to the apiserver (default 20) --kubeconfig string Paths to a kubeconfig. Only required if out-of-cluster. --legacy_stderr_threshold_behavior If true, stderrthreshold is ignored when logtostderr=true (legacy behavior). If false, stderrthreshold is honored even when logtostderr=true --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) --metrics-bind-address string The address the metric endpoint binds to. (default ":8080") --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) --port int Port number to serve webhooks. Defaults to 9443 (default 9443) --profiling-bind-address string The address the profiling would be exposed on. --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 unless -legacy_stderr_threshold_behavior=false) -v, --v Level number for the log level verbosity --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging --zap-devel Development Mode defaults(encoder=consoleEncoder,logLevel=Debug,stackTraceLevel=Warn). Production Mode defaults(encoder=jsonEncoder,logLevel=Info,stackTraceLevel=Error) --zap-encoder encoder Zap log encoding (one of 'json' or 'console') --zap-log-level level Zap Level to configure the verbosity of logging. Can be one of 'debug', 'info', 'error', 'panic' or any integer value > 0 which corresponds to custom debug levels of increasing verbosity --zap-stacktrace-level level Zap Level at and above which stacktraces are captured (one of 'info', 'error', 'panic'). --zap-time-encoding time-encoding Zap time encoding (one of 'epoch', 'millis', 'nano', 'iso8601', 'rfc3339' or 'rfc3339nano'). Defaults to 'epoch'.