Prometheus 不能访问k8s的中的一些metrics的问题（controller-manager、scheduler、etcd、proxy）

主要有三个点

controller-manager、scheduler、etcd、proxy

参考：

https://www.cnblogs.com/ltaodream/p/15448953.html

kube-scheduler

在每台master节点执行

vim /etc/kubernetes/manifests/kube-scheduler.yaml

将

--bind-address=127.0.0.1

改为

--bind-address=0.0.0.0

kube-controller-manager

vim /etc/kubernetes/manifests/kube-controller-manager.yaml

将

--bind-address=127.0.0.1

改为

--bind-address=0.0.0.0

etcd

vi /etc/kubernetes/manifests/etcd.yaml

将

--listen-metrics-urls=http://127.0.0.1:2381

改为

--listen-metrics-urls=http://127.0.0.1:2381,http://你主机的IP地址（也就是图上serviceMonitor中展示的访问不通的地址）:2381

参考：serviceMonitor/default/kube-prometheus-stack-kube-etcd detect Incorrect metric port and connection reset by peer · Issue #1005 · prometheus-community/helm-charts · GitHub

proxy

kubectl edit cm/kube-proxy -n kube-system


Change from
metricsBindAddress: ""
Change to
metricsBindAddress: 0.0.0.0:10249

删除，重部
kubectl delete pod -l k8s-app=kube-proxy -n kube-system

参考：k8s添加promethues-operater作为监控后无法监控kube-proxy的解决方法_kube-prometheus监控不到kube-proxy-CSDN博客

重启kubelet

systemctl restart kubelet.service

ETCD grafana

模板号3070