Dan Winship 3948f16ff4 Add iptables.Monitor, use it from kubelet and kube-proxy ... Kubelet and kube-proxy both had loops to ensure that their iptables rules didn't get deleted, by repeatedly recreating them. But on systems with lots of iptables rules (ie, thousands of services), this can be very slow (and thus might end up holding the iptables lock for several seconds, blocking other operations, etc). The specific threat that they need to worry about is firewall-management commands that flush *all* dynamic iptables rules. So add a new iptables.Monitor() function that handles this by creating iptables-flush canaries and only triggering a full rule reload after noticing that someone has deleted those chains.		2019-09-17 10:19:26 -04:00
..
BUILD	update BUILD files	2017-10-15 18:18:13 -07:00
fake.go	Add iptables.Monitor, use it from kubelet and kube-proxy	2019-09-17 10:19:26 -04:00