Quan Tian ca8c27c480 kube-proxy: do not delete previously stale but currently active chains ...

In some cases a chain could change from stale to active, but once it's
added to staleChains it would always be deleted once. When the proxier
tries to delete a previously stale but currently active chain, it would
fail and lead to errors, though it won't cause real problem thanks to
kernel's validation.

The commit removes a chain from staleChains if it becomes active.

Signed-off-by: Quan Tian <qtian@vmware.com>

2024-01-08 17:53:52 +08:00

..

helpers_test.go

Properly build-tag the Linux kube-proxy backend code

2023-12-18 20:20:51 -05:00

proxier_test.go

kube-proxy: do not delete previously stale but currently active chains

2024-01-08 17:53:52 +08:00

proxier.go

kube-proxy: do not delete previously stale but currently active chains

2024-01-08 17:53:52 +08:00