Stop talking to the kubelet unsecured port

[bboreham]

When running under Kubernetes, the probe will try to talk to kubelet on 10255, unsecured, if it doesn't know the node name. We should not assume unsecured access.

There is a secured port at 10250; probably we have access to credentials. Or we could just remove that code and insist on knowing the node name.

Kubeadm removes the unsecured port by default: https://github.com/kubernetes/kubernetes/pull/64187

This is possibly the underlying issue for #3104 (OpenShift)

[SaberYoun6]

I was wonder how can I assist in you solving your problem?

[bboreham]

@yuriprym I'm not clear what kind of advice you need. Given other developments it's probably best to remove the code that talks to kubelet and rely on filtering by node name (if per-node reporting is still enabled). So the main work is in checking the system still works, and considering how to warn the user if they don't supply a node name.