kube-proxy will not expose metrics endpoint by default with kind setup. We need to manually edit kube-proxy configmap and delete the pod so as to have it recreated properly.

This is something that could be improved on kind's side by having an option to enable metrics exposition by default (see kubernetes-sigs/kind#2184), however we might can to tackle this on our side and have the deployer to edit the confgimap and delete the Pod so as to have a new one created with the proper configuration. We can first check if the endpoint is reachable so as to avoid recreating the pod without reason.

@mtojek @ycombinator what do you think about this?