metrics-server pod fails readiness prob

[arms11]

trafficstars

Following the instructions and after running vagrant up when I checked all pods in the kube-system namespace, I found the metrics-server pod is not in ready state. This prevents kubectl top ... commands from running successfully.

calico-kube-controllers-7c845d499-r8t4l   1/1     Running   0          5m10s
calico-node-fx4k7                         1/1     Running   0          2m22s
calico-node-r8n9j                         1/1     Running   0          5m10s
coredns-64897985d-wlnx6                   1/1     Running   0          5m10s
coredns-64897985d-zt999                   1/1     Running   0          5m10s
etcd-master-node                          1/1     Running   0          5m19s
kube-apiserver-master-node                1/1     Running   0          5m19s
kube-controller-manager-master-node       1/1     Running   0          5m26s
kube-proxy-4nxf9                          1/1     Running   0          2m22s
kube-proxy-vzhl9                          1/1     Running   0          5m10s
kube-scheduler-master-node                1/1     Running   0          5m19s
metrics-server-99c6c96cf-8jdpm            0/1     Running   0          5m10s

I could not find a way to revive this following other related posts that mainly focuses on using --kubelet-insecure-tls which is already present. Not sure why this is stuck in this way.