You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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:
The text was updated successfully, but these errors were encountered: