26801d6541
Since kube-proxy in LocalModeNodeCIDR needs to obtain the PodCIDR assigned to the node it watches for the Node object. However, kube-proxy startup process requires to have these watches in different places, that opens the possibility of having a race condition if the same node is recreated and a different PodCIDR is assigned. Initializing the second watch with the value obtained in the first one allows us to detect this situation. Change-Id: I6adeedb6914ad2afd3e0694dcab619c2a66135f8 Signed-off-by: Antonio Ojea <aojea@google.com> |
||
|---|---|---|
| .. | ||
| conntrack.go | ||
| init_others.go | ||
| init_windows.go | ||
| server_others_test.go | ||
| server_others.go | ||
| server_test.go | ||
| server_windows.go | ||
| server.go | ||