What problem are you trying to solve?

Currently, changing --controller-log-level does not change klog's level.

How should the problem be solved?

Map the -v levels of klog to panic, fatal, error, warn, info, debug. Kubernetes documents the log levels.

Perhaps:

• -v 0 - panic, fatal, error, warn
• -v 1 - info
• -v 2 - info
• -v 3 - debug
• -v 4 - debug
• -v 5 - Not sure, maybe we should add a trace level? @siggy found differences between logging at -v 8 even. When does it stop?

Note, along with -v for log levels, klog also uses stderrthreshold. The possible values for that are info, warning, error, fatal. These can also be mapped to the linkerd log levels.