Antonio Ojea 108c2aebd4 portmap plugin should flush previous udp connections ... conntrack does not have any way to track UDP connections, so it relies on timers to delete a connection. The problem is that UDP is connectionless, so a client will keep sending traffic despite the server has gone, thus renewing the conntrack entries. Pods that use portmaps to expose UDP services need to flush the existing conntrack entries on the port exposed when they are created, otherwise conntrack will keep sending the traffic to the previous IP until the connection age (the client stops sending traffic) Signed-off-by: Antonio Ojea <aojea@redhat.com>		2020-11-23 16:29:52 +01:00
..
errors	[DO NOT REVIEW] vendor upate to remove useless dependencies	2020-03-17 14:30:28 +08:00
hns	Remove extraneous test file in Windows plugin	2020-09-09 16:12:54 +00:00
ip	ptp, bridge: disable accept_ra on the host-side interface	2020-05-12 15:54:23 +02:00
ipam	pkg/ipam : use delegateArgs instead of env set/unset in ipam.ExecDel	2019-06-18 21:02:01 +08:00
ns	Fix race condition in GetCurrentNS	2020-08-21 13:05:21 +08:00
testutils	portmap plugin should flush previous udp connections	2020-11-23 16:29:52 +01:00
utils	portmap plugin should flush previous udp connections	2020-11-23 16:29:52 +01:00