Generic Coexistence section in README

[coryrc]

/kind docs

I'd like to update README.md to have a "Coexistence" section, like where glog is now, but suggesting the use of SetLogger() with everything supported by logr: https://github.com/go-logr/logr

Is this desirable?

[neolit123]

the SetLogger() PR was reverted. this might get added again in version 2.x.
#97

[neolit123]

/priority awaiting-more-evidence

[coryrc]

That itself was reverted: #98

so it is back?:

klog/klog.go

Line 775 in 8422fac

// klog.SetLogger(zapr.NewLogger(zapLog))

[neolit123]

ok i missed the revert of the revert.
so it becomes a question whether we should document features in the readme that are not yet part of the next release.

/assign @dims @DirectXMan12

[neolit123]

"Coexistence" section

i would go with a more descriptive title, but can't think of a good one right now.

[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.