Andy Goldstein ea78586832 Re-allow 0 for kube-proxy conntrack settings ... When kube-proxy was refactored to use a configuration file, the ability to use 0 for conntrack min, max, max per core, and tcp timeouts was inadvertently broken; if you specified 0, it would instead apply the default value from defaults.go. This change restores the ability to use 0 to mean 0. Signed-off-by: Andy Goldstein <andy.goldstein@gmail.com>		2017-11-07 14:45:30 -05:00
..
app	Re-allow 0 for kube-proxy conntrack settings	2017-11-07 14:45:30 -05:00
BUILD	update BUILD files	2017-10-15 18:18:13 -07:00
proxy.go	Run go fmt	2017-08-18 16:03:25 +08:00