{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/28515","repository_url":"https://api.github.com/repos/kubernetes/kubernetes","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/28515/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/28515/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/28515/events","html_url":"https://github.com/kubernetes/kubernetes/issues/28515","id":163966243,"number":28515,"title":"kube-dns v15+ cannot set verbosity","user":{"login":"fluxrad","id":563666,"avatar_url":"https://avatars.githubusercontent.com/u/563666?v=3","gravatar_id":"","url":"https://api.github.com/users/fluxrad","html_url":"https://github.com/fluxrad","followers_url":"https://api.github.com/users/fluxrad/followers","following_url":"https://api.github.com/users/fluxrad/following{/other_user}","gists_url":"https://api.github.com/users/fluxrad/gists{/gist_id}","starred_url":"https://api.github.com/users/fluxrad/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fluxrad/subscriptions","organizations_url":"https://api.github.com/users/fluxrad/orgs","repos_url":"https://api.github.com/users/fluxrad/repos","events_url":"https://api.github.com/users/fluxrad/events{/privacy}","received_events_url":"https://api.github.com/users/fluxrad/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2016-07-05T23:09:03Z","updated_at":"2016-11-11T19:52:37Z","closed_at":"2016-07-08T06:56:00Z","body":"When replacing kube-dns v11 (as defined w/ the v1.2.4 release) with v15 in the v1.3.0 release, we notice that the `skydns` container inside the `kube-dns` pod is overly verbose. This appears to be due to an inability to turn of `Info` logging within [dns.go](https://github.com/kubernetes/kubernetes/blob/master/pkg/dns/dns.go#L583). Neither the `--v` flag, nor the `--stderrthreshold=2` flags appear to have any impact. On a 65 node cluster with approximately 1700 pods, this results in a log load of over 10,000 log entries per second. Can we implement a mechanism to turn off Info-level logging from kubedns?\n\nSee also CoreOS kubernetes issue [555](https://github.com/coreos/coreos-kubernetes/pull/555#issuecomment-229530165).\n"},"comment":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/comments/260041100","html_url":"https://github.com/kubernetes/kubernetes/issues/28515#issuecomment-260041100","issue_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/28515","id":260041100,"user":{"login":"joshk0","id":5368926,"avatar_url":"https://avatars.githubusercontent.com/u/5368926?v=3","gravatar_id":"","url":"https://api.github.com/users/joshk0","html_url":"https://github.com/joshk0","followers_url":"https://api.github.com/users/joshk0/followers","following_url":"https://api.github.com/users/joshk0/following{/other_user}","gists_url":"https://api.github.com/users/joshk0/gists{/gist_id}","starred_url":"https://api.github.com/users/joshk0/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/joshk0/subscriptions","organizations_url":"https://api.github.com/users/joshk0/orgs","repos_url":"https://api.github.com/users/joshk0/repos","events_url":"https://api.github.com/users/joshk0/events{/privacy}","received_events_url":"https://api.github.com/users/joshk0/received_events","type":"User","site_admin":false},"created_at":"2016-11-11T19:52:37Z","updated_at":"2016-11-11T19:52:37Z","body":"@rileylark, when I went to Kubernetes v1.4 the issue went away, I think."}}
{"actor":{"display_login":"joshk0"}}