Confusing arguments

[adrianlzt]

/kind bug

What steps did you take and what happened:
It is kinda difficult to configure logging, as arguments don't work as expected.

Doc is outdated and still show glog:
https://godoc.org/k8s.io/klog

-logtostderr=false

But in code is defaulted to true:

flagset.BoolVar(&logging.toStderr, "logtostderr", true, "log to standard error instead of files")

Examples of weird behaviours.

No initialization shows >=error:

klog.Info("info")
klog.Error("error")

But if klog is initializated, it shows info and error (because flag logtostderr is set to true):

klog.InitFlags(nil)
flag.Parse()
klog.Info("info")
klog.Error("error")

Also weird because default value for stderrthreshold is ERROR and the doc says:

Log events at or above this severity are logged to standard error as well as to files

Then I switch off logging to stderr:

klog.InitFlags(nil)
flag.Set("logtostderr", "false")
flag.Parse()
klog.Info("info")
klog.Error("error")

And now it keeps logging to stderr but just error level.

What did you expect to happen:
Updated doc and a understandable behaviour.

[DirectXMan12]

There's two issues at play here:

1. The flag initialization issue (that's pretty sub-optimal)
2. The confusing nature of glog/klog flags and stderror -- that's a bit harder to fix due to backwards compat constraints, but we want to do it. You're not the first person to be confused/frustrated by that.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.