Dan Winship 169604d906 Validate single-stack --nodeport-addresses sooner ... In the dual-stack case, iptables.NewDualStackProxier and ipvs.NewDualStackProxier filtered the nodeport addresses values by IP family before creating the single-stack proxiers. But in the single-stack case, the kube-proxy startup code just passed the value to the single-stack proxiers without validation, so they had to re-check it themselves. Fix that.		2023-01-03 09:01:45 -05:00
..
conntrack.go	replace deprecated io/ioutil with os and io for cmd	2022-02-01 13:59:41 +08:00
init_others.go	generated: Run hack/update-gofmt.sh	2021-08-24 15:47:49 -04:00
init_windows.go	Fix health check from Google's Load Balancer	2022-03-11 22:34:59 -08:00
server_others_test.go	kube-proxy wait for cluster cidr skip delete events	2022-10-18 19:29:09 +00:00
server_others.go	Validate single-stack --nodeport-addresses sooner	2023-01-03 09:01:45 -05:00
server_test.go	kube-proxy: add a flag to disables the allowing NodePort services to be accessed via localhost	2022-11-02 16:17:52 +08:00
server_windows.go	use klog.InfoS instead of klog.V(0).Info-proxy part	2022-12-29 11:16:51 +08:00
server.go	kube-proxy: add a flag to disables the allowing NodePort services to be accessed via localhost	2022-11-02 16:17:52 +08:00