helm install prometheus-operator

来源：12-6 监控部署实战 - Helm+PrometheusOperator

pkarqi001

2020-03-10

[root@192-168-31-249-master1 ~]# helm install --name imooc-prom --set rbacEnable=true --namespace=monitoring ./prometheus-operator
Error: validation failed: [unable to recognize “”: no matches for kind “Alertmanager” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “Prometheus” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “PrometheusRule” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “PrometheusRule” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “PrometheusRule” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “PrometheusRule” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “PrometheusRule” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “PrometheusRule” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “PrometheusRule” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “PrometheusRule” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “PrometheusRule” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “PrometheusRule” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “PrometheusRule” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “PrometheusRule” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “PrometheusRule” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “PrometheusRule” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “PrometheusRule” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “PrometheusRule” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “PrometheusRule” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “PrometheusRule” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “PrometheusRule” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “PrometheusRule” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “PrometheusRule” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “PrometheusRule” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “PrometheusRule” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “PrometheusRule” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “ServiceMonitor” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “ServiceMonitor” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “ServiceMonitor” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “ServiceMonitor” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “ServiceMonitor” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “ServiceMonitor” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “ServiceMonitor” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “ServiceMonitor” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “ServiceMonitor” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “ServiceMonitor” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “ServiceMonitor” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “ServiceMonitor” in version “monitoring.coreos.com/v1”, unable to recognize “”: no matches for kind “ServiceMonitor” in version “monitoring.coreos.com/v1”]

写回答

3回答

pkarqi001

提问者

2020-03-17

null

pkarqi001

提问者

2020-03-13

helm 版本升级到2.14.3 报错如下

[root@192-168-31-249-master1 ~]# kubectl get pods -n monitoring | grep -v Running

NAME READY STATUS RESTARTS AGE

alertmanager-imooc-prom-prometheus-oper-alertmanager-0 1/2 CrashLoopBackOff 11 33m

prometheus-imooc-prom-prometheus-oper-prometheus-0 0/3 ContainerCreating 0 114s

报错

1、

Type Reason Age From Message

---- ------ ---- ---- -------

Warning FailedMount 33s kubelet, 192-168-31-216-node1 Unable to mount volumes for pod "prometheus-imooc-prom-prometheus-oper-prometheus-0_monitoring(451f3d91-647f-11ea-a8f0-000c29da459b)": timeout expired waiting for volumes to attach or mount for pod "monitoring"/"prometheus-imooc-prom-prometheus-oper-prometheus-0". list of unmounted volumes=[secret-etcd-certs]. list of unattached volumes=[config config-out prometheus-imooc-prom-prometheus-oper-prometheus-rulefiles-0 secret-etcd-certs prometheus-imooc-prom-prometheus-oper-prometheus-db imooc-prom-prometheus-oper-prometheus-token-g62sq]

Warning FailedMount 28s (x9 over 2m36s) kubelet, 192-168-31-216-node1 MountVolume.SetUp failed for volume "secret-etcd-certs" : secret "etcd-certs" not found

Normal Scheduled <invalid> default-scheduler Successfully assigned monitoring/prometheus-imooc-prom-prometheus-oper-prometheus-0 to 192-168-31-216-node1

[root@192-168-31-249-master1 ~]# kubectl describe pod prometheus-imooc-prom-prometheus-oper-prometheus-0 -n monitoring

报错2:

Events:

Type Reason Age From Message

---- ------ ---- ---- -------

Normal Pulled 35m kubelet, 192-168-31-37-node2 Container image "quay.io/coreos/configmap-reload:v0.0.1" already present on machine

Normal Created 35m kubelet, 192-168-31-37-node2 Created container config-reloader

Normal Started 35m kubelet, 192-168-31-37-node2 Started container config-reloader

Normal Created 34m (x4 over 35m) kubelet, 192-168-31-37-node2 Created container alertmanager

Normal Started 34m (x4 over 35m) kubelet, 192-168-31-37-node2 Started container alertmanager

Normal Pulled 33m (x5 over 35m) kubelet, 192-168-31-37-node2 Container image "quay.io/prometheus/alertmanager:v0.16.2" already present on machine

Warning BackOff 27s (x168 over 35m) kubelet, 192-168-31-37-node2 Back-off restarting failed container

Normal Scheduled <invalid> default-scheduler Successfully assigned monitoring/alertmanager-imooc-prom-prometheus-oper-alertmanager-0 to 192-168-31-37-node2

不知道是不是这个原因

https://blog.csdn.net/u011933777/article/details/102722700

etc/kubernetes/pki/etcd/server.crt 找不到这个文件啥时候生成的？（server.crt ）

pkarqi001

刘果国

谢谢 prometheus-imooc-prom-prometheus-oper-prometheus-0 这个容器已经正常启动。*.pem 文件用配置集群的就可以，但是貌似路径就必须就是配置文件里的那样 [root@192-168-31-249-master1 ~]# kubectl get pod -n monitoring NAME READY STATUS RESTARTS AGE alertmanager-imooc-prom-prometheus-oper-alertmanager-0 1/2 CrashLoopBackOff 205 16h Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Pulled 7m3s (x205 over 16h) kubelet, 192-168-31-216-node1 Container image "quay.io/prometheus/alertmanager:v0.16.2" already present on machine Warning BackOff 2m14s (x4708 over 16h) kubelet, 192-168-31-216-node1 Back-off restarting failed container [root@192-168-31-249-master1 ~]# 这个容器不正常是因为拉取容器的地址不行么？

2020-03-14

共4条回复