/kind feature

Describe the solution you'd like

In Kubernetes, we currently use the traditional klog output handling code, with all the cruft that has accumulated there. Since the deprecation of klog flags, none of that code does anything anymore, but we also cannot remove it because it is part of klog/v2.

What would be useful for Kubernetes would be a klogr Logger which:

• has its own, simple output handling, with support for buffering of info messages just as in zapr (new feature)
• support vmodule (feature parity)
• same output format (no usability changes)

The restructuring of klog into separate packages for vmodule and formatting should make the implementation of such a logger relatively easy.