Clayton Coleman ae2f6a833a Reduce volume of logs generated at v(3) ... Node controller is generating a huge amount of logging at v(3) that is more appropriate for v(5). Split the log into two levels and ensure it also ends up on one line (so grep works). The pod manager generates a v(4) pod output on sync that always contains a newline - since the size of the pod is so excessive in output, kick it to v(5) for deep debugging (we're pretty happy with this loop).		2016-02-20 15:29:05 -05:00
..
doc.go	adjust package name for pkg/controller directory	2015-10-12 09:51:27 +08:00
nodecontroller_test.go	generate fake client for release_1_2	2016-02-17 16:10:02 -08:00
nodecontroller.go	Reduce volume of logs generated at v(3)	2016-02-20 15:29:05 -05:00
rate_limited_queue_test.go	Add FakeNeverRateLimitter	2016-02-08 11:06:25 +01:00
rate_limited_queue.go	RateLimiter: change CanAccept() to TryAccept()	2015-11-23 16:42:53 -08:00