kubelet_hostname_override leads to some ugly errors in kube-proxy

[ravishivt]

When kubelet_hostname_override setting is enabled, the kube-proxy gives the following startup errors:

E0112 06:07:10.274956       1 server.go:421] Can't get Node "kube1", assuming iptables proxy, err: nodes "kube1" not found
W0112 06:07:10.277165       1 server.go:468] Failed to retrieve node info: nodes "kube1" not found
W0112 06:07:10.277296       1 proxier.go:249] invalid nodeIP, initialize kube-proxy with 127.0.0.1 as nodeIP

I'm not sure of the symptoms of this error. I was having multiple networking issues so it was hard to correlate which error messages caused which issues. The errors can be cleared though by passing the --hostname-override setting to kube-proxy as well as kubelet, which is apparently required according to kubernetes/kubernetes#18104 (comment).

Full kube-proxy logs

E0112 06:07:10.274956       1 server.go:421] Can't get Node "kube1", assuming iptables proxy, err: nodes "kube1" not found
I0112 06:07:10.276098       1 server.go:215] Using iptables Proxier.
W0112 06:07:10.277165       1 server.go:468] Failed to retrieve node info: nodes "kube1" not found
W0112 06:07:10.277296       1 proxier.go:249] invalid nodeIP, initialize kube-proxy with 127.0.0.1 as nodeIP
W0112 06:07:10.277347       1 proxier.go:254] clusterCIDR not specified, unable to distinguish between internal and external traffic
I0112 06:07:10.277415       1 server.go:227] Tearing down userspace rules.
I0112 06:07:10.287037       1 conntrack.go:81] Set sysctl 'net/netfilter/nf_conntrack_max' to 131072
I0112 06:07:10.287505       1 conntrack.go:66] Setting conntrack hashsize to 32768
I0112 06:07:10.287732       1 conntrack.go:81] Set sysctl 'net/netfilter/nf_conntrack_tcp_timeout_established' to 86400
I0112 06:07:10.287818       1 conntrack.go:81] Set sysctl 'net/netfilter/nf_conntrack_tcp_timeout_close_wait' to 3600

[v1k0d3n]

sorry took so long @ravishivt! @aric49 thanks for taking this on, and cleaning things up. resolves issue #45