log level broken by a previous PR

[ipochi]

A prior change in #685 introduced a condition (if local.Lookup("v") == nil) before setting the default klog verbosity level. This condition was incorrect because klog.InitFlags() always defines the -v flag, meaning the default verbosity was never being applied. This caused the effective log level to fall back to klog's default of 0 instead of the intended 4.

Reverting the code should solve this issue.

[makhov]

@ipochi thanks fot noticing! Looks like I accidentally messed up an order of thigs. As I described in the PR comments, I'm not a big fun of reverting the change. Let me just fix it.

[ipochi]

@makhov

I'm a bit confused as to what was wrong with the code before #785 was merged.

The code did as expected:

If you don't pass the v flag, it's 4
If you do, that will be set.

[makhov]

Actually nothing. Just my assumptions were wrong, sorry.
On the other hand, I've heard a lot of complains that konnectivity is too noisy, maybe it makes sense to reconsider the default value