deployment LOG_LEVEL don't have effect

[like-inspur]

I install k8s-injector referencing examples/kubernetes/deployment.yaml, but no matter what value I config for LOG_LEVEL, the pod always output info level log and so many kube-probe logs like this:
10.233.98.0 - - [15/Oct/2019:02:05:07 +0000] "POST /mutate?timeout=30s HTTP/2.0" 200 74 "" "kube-apiserver-admission"
I1015 02:05:07.968371 1 webhook.go:584] Ready to write reponse ...
10.233.98.0 - - [15/Oct/2019:02:05:07 +0000] "POST /mutate?timeout=30s HTTP/2.0" 200 74 "" "kube-apiserver-admission"
10.110.18.103 - - [15/Oct/2019:02:05:10 +0000] "GET /health HTTP/2.0" 200 12 "" "kube-probe/1.14"
10.110.18.103 - - [15/Oct/2019:02:05:13 +0000] "GET /health HTTP/2.0" 200 12 "" "kube-probe/1.14"
10.110.18.103 - - [15/Oct/2019:02:05:20 +0000] "GET /health HTTP/2.0" 200 12 "" "kube-probe/1.14"
10.110.18.103 - - [15/Oct/2019:02:05:23 +0000] "GET /health HTTP/2.0" 200 12 "" "kube-probe/1.14"

[byxorna]

@like-inspur LOG_LEVEL gets passed to glog's -v flag, but the log messages you show above are generated by the HTTP logging middleware (see https://github.com/tumblr/k8s-sidecar-injector/blob/master/cmd/main.go#L183) that unfortunately does not use glog. Currently, there is no way to reduce logging verbosity of HTTP responses.