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
..
2017-11-05 06:49:30 -08:00
2017-10-15 18:18:13 -07:00
2017-11-06 22:20:20 -08:00
2017-10-30 19:54:02 +01:00
2017-10-15 18:18:13 -07:00
2017-10-15 18:18:13 -07:00
2017-11-06 14:04:33 +01:00
2017-11-07 15:19:20 +08:00
2017-11-03 10:00:12 -07:00
2017-10-15 18:18:13 -07:00
2017-10-28 03:44:46 +00:00
2017-10-15 18:18:13 -07:00
2017-11-04 11:38:57 +08:00
2017-10-15 18:18:13 -07:00
2017-11-02 09:29:55 +01:00
2017-11-06 06:34:40 -08:00
2017-11-06 23:19:25 -08:00
2017-10-23 11:15:48 -07:00
2017-11-06 13:05:33 +01:00
2017-11-06 16:57:10 -08:00
2017-10-15 18:18:13 -07:00
2017-11-07 14:45:30 -05:00
2017-10-27 11:07:01 -04:00
2017-11-07 06:03:16 -08:00
2017-10-15 18:18:13 -07:00
2017-10-16 02:22:10 -04:00
2017-10-16 02:22:10 -04:00
2017-10-15 18:18:13 -07:00
2017-10-15 18:18:13 -07:00
2017-11-06 23:19:15 -08:00
2017-10-15 18:18:13 -07:00
2017-11-03 14:33:16 -07:00
2017-10-15 18:18:13 -07:00
2017-10-13 07:06:22 -04:00
2017-10-16 16:36:44 +08:00
2017-01-19 11:29:16 -08:00