$ kubectl get pods --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system coredns-558bd4d5db-h4968 1/1 Running 0 18m
kube-system coredns-558bd4d5db-klb5t 1/1 Running 0 18m
kube-system etcd-ip-172-31-12-77 1/1 Running 0 18m
kube-system kube-apiserver-ip-172-31-12-77 1/1 Running 0 18m
kube-system kube-controller-manager-ip-172-31-12-77 1/1 Running 0 18m
kube-system kube-proxy-5p7gr 1/1 Running 0 18m
kube-system kube-scheduler-ip-172-31-12-77 1/1 Running 0 18m
kube-system metrics-server-6dfddc5fb8-vllgm 0/1 Running 0 17m
kube-system weave-net-gqrtg 2/2 Running 0 18m
root@ip-172-31-12-77:/home/ubuntu#
$ kubectl describe pod metrics-server-6dfddc5fb8-vllgm -n=kube-system
Normal Created 16m kubelet Created container metrics-server
Normal Started 16m kubelet Started container metrics-server
Warning Unhealthy 62s (x89 over 15m) kubelet Readiness probe failed: HTTP probe failed with statuscode: 500
$ kubectl logs deployment/metrics-server -n kube-system
E0713 16:52:04.774647 1 scraper.go:139] "Failed to scrape node" err="Get \"https://172.31.12.77:10250/stats/summary?only_cpu_and_memory=true\": x509: cannot validate certificate for 172.31.12.77 because it doesn't contain any IP SANs" node="ip-172-31-12-77"
172.31.12.77Solution:
- Download https://github.com/kubernetes-sigs/metrics-server/releases/latest/download/components.yaml
- Modify and add "- --kubelet-insecure-tls" in deployment.spec.template.spec.containers.args
- kubectl apply -f components.yaml
- kubectl top nodes
- kubectl top pod kube-proxy-5p7gr -n=kube-system
Reference
- https://stackoverflow.com/questions/64767239/kubernetes-metrics-server-not-running
Latest posts by rajeshkumar (see all)
- The Three Pillars of Digital Resilience in 2025: Database Administration, Cybersecurity, and Vulnerability Assessment - September 24, 2025
- Avionics Technician: The Backbone of Modern Aviation - September 12, 2025
- Top 20 Computer Vision Libraries - August 26, 2025