Phil Cameron 965cf128b6 Remove iptables log on restore failure ...

Don't log the set of rules at v2 in kube-proxy on error.
The rules are displayed at v5 before the restore is attempted.

In a large cluster the report can generate up to 100000 lines.
A partial report is only helpful if the problem is displayed
in the partial report.

2017-10-27 09:14:35 -04:00

..

config

update BUILD files

2017-10-15 18:18:13 -07:00

healthcheck

update BUILD files

2017-10-15 18:18:13 -07:00

iptables

Remove iptables log on restore failure

2017-10-27 09:14:35 -04:00

ipvs

fix review comments

2017-10-24 10:30:38 +08:00

metrics

add proxy metrics in app level

2017-10-16 21:10:51 +08:00

userspace

Merge pull request #47699 from supereagle/fix-typos

2017-10-17 02:35:52 -07:00

util

update BUILD files

2017-10-15 18:18:13 -07:00

winkernel

Merge pull request #53708 from m1093782566/cleanup-winkernel-proxy

2017-10-20 22:46:12 -07:00

winuserspace

update BUILD files

2017-10-15 18:18:13 -07:00

BUILD

add proxy metrics in app level

2017-10-16 21:10:51 +08:00

doc.go

Use Go canonical import paths

2016-07-16 13:48:21 -04:00

OWNERS

add m1093782566 to pkg/proxy/OWNERS

2017-10-13 11:39:25 +08:00

types.go

kube-proxy: OnServiceUpdate takes pointers

2017-04-03 17:19:39 -07:00