Fix unified flag in --logging-format description

[chymy]

Signed-off-by: chymy chang.min1@zte.com.cn

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
In k8s components, the command line parameters are all combined with -, not _.
So in --logging-format description,

--logging-format string
                Sets the log format. Permitted formats: "json", "text".
                Non-default formats don't honor these flags: --add_dir_header, --alsologtostderr, --log_backtrace_at, --log_dir,
                --log_file, --log_file_max_size, --logtostderr, --one_output, --skip_headers, --skip_log_headers, --stderrthreshold,
                --vmodule, --log-flush-frequency.

should be:

--logging-format string
                Sets the log format. Permitted formats: "json", "text".
                Non-default formats don't honor these flags: --add-dir-header, --alsologtostderr, --log-backtrace-at, --log-dir,
                --log-file, --log-file-max-size, --logtostderr, --one-output, --skip-headers, --skip-log-headers, --stderrthreshold,
                --vmodule, --log-flush-frequency.

To be consistent with global flags：

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
  -h, --help
                help for kube-scheduler
      --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)
      --log-flush-frequency duration
                Maximum number of seconds between log flushes (default 5s)
      --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
      --skip-headers
                If true, avoid header prefixes in the log messages
      --skip-log-headers
                If true, avoid headers when opening log files

in order to prevent the reader from making mistakes by using underlined flags, it is better to replace _ with - in --logging-format description

e.g.:

# kube-controller-manager --add_dir_header
Error: unknown flag: --add_dir_header

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

Hi @chymy. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[fedebongio]

/remove-sig api-machinery

[chymy]

/assign @dashpole

[dashpole]

cc @serathius
/ok-to-test
/approve

[dashpole]

/remove-sig cluster-lifecycle

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chymy, dashpole

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• staging/src/k8s.io/component-base/logs/OWNERS [dashpole]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[dashpole]

/triage accepted
/priority backlog

[chymy]

/test pull-kubernetes-e2e-kind-ipv6

[chymy]

/test pull-kubernetes-bazel-test

[249043822]

/lgtm

[chymy]

/test pull-kubernetes-bazel-test

[chymy]

/test pull-kubernetes-bazel-test