Brad Davidson 374271e9a0 Collect IPs from all pods before deciding to use internal or external addresses (#2909) ... * Collect IPs from all pods before deciding to use internal or external addresses @Taloth correctly noted that the code that iterates over ServiceLB pods to collect IP addresses was failing to add additional internal IPs once the map contained ANY entry from a previous node. This may date back to when ServiceLB used a Deployment instead of a DaemonSet, so there was only ever a single pod. The new behavior is to collect all internal and external IPs, and then construct the address list of a single type - external if there are any, otherwise internal. https://github.com/k3s-io/k3s/issues/1652#issuecomment-774497788 Signed-off-by: Brad Davidson <brad.davidson@rancher.com> Co-authored-by: Brian Downs <brian.downs@gmail.com>		2021-02-09 16:26:57 -08:00
..
controller.go	Collect IPs from all pods before deciding to use internal or external addresses (#2909)	2021-02-09 16:26:57 -08:00