Repository navigation
Logging should be streamlined #291
Description
The current controller runtime offers a log package that includes a zap logger and lets users to bring their own logger by implementing https://github.com/go-logr/logr interfaces. Most of the other tools in the Kubernetes ecosystem use klog as the main logging point, which makes it hard to have a single output and logger given that klog doesn't expose any interface that implements logr interfaces.
Some related issues in the community:
Activity
DirectXMan12 commentedon Jan 15, 2019
github.com/go-logr/glogr should be trivially adaptable to klog (it was originally written for glog). We'll see how klog evolves, but getting that situation squared away is something I would definitely like to do.
DirectXMan12 commentedon Jan 15, 2019
/priority important-soon
DirectXMan12 commentedon Mar 6, 2019
kubernetes/klog#37 at least partially solves this problem with its klogr package. The other half is being worked on it kubernetes/klog#20.
Merge pull request #291 from briantkennedy/master