monitoring/kube-controller-manager
来源:12-6 监控部署实战 - Helm+PrometheusOperator

慕移动6259844
2021-03-11
请老师帮看下
-
kubectl 安装的 kube-prometheus 0.6
-
kubernete 1.18
-
在执行完成kube-prometheus完后,发现kube-controller-manager/0 (0/0 up), monitoring/kube-scheduler(0/0);
其他的Endpoint都是正常的 -
对controller进行了下面的操作
apiVersion: v1
kind: Service
metadata:
namespace: kube-system
name: kube-controller-manager
labels:
k8s-app: kube-controller-manager
spec:
type: ClusterIP
clusterIP: None
ports:
- name: https-metrics
port: 10252
targetPort: 10252
protocol: TCP
apiVersion: v1
kind: Endpoints
metadata:
labels:
k8s-app: kube-controller-manager
name: kube-controller-manager
namespace: kube-system
subsets:
- addresses:
- ip: 192.168.200.128
ports: - name: https-metrics
port: 10252
protocol: TCP
- ip: 192.168.200.128
5.刷新Prometheus后
5.1 显示为monitoring/kube-controller-manager/0 (0/1 up)
https://192.168.247.200:10252/metrics —》error: server returned HTTP status 403 Forbidden
1回答
-
刘果国
2021-03-11
kube-controller-manager都不正常的话集群都不能用的,不能搞prometheus哈。先排查基础组件的启动日志。另外多放些截图,文字太难看了
00