也遇到的同样问题,查看alert_manager日志只有两条:
level=info ts=2021-03-05T02:55:03.591Z caller=main.go:216 msg=“Starting Alertmanager” version=“(version=0.21.0, branch=HEAD, revision=4c6c03ebfe21009c546e4d1e9b92c371d67c021d)”
level=info ts=2021-03-05T02:55:03.591Z caller=main.go:217 build_context=“(go=go1.14.4, user=root@dee35927357f, date=20200617-08:54:02)”
describe pod 信息如下:
Containers:
alertmanager:
Container ID: docker://d16361a9d555e4796f4e8d7ec2722f5f057069af3bb63f4d58dbeb3fccfb8c72
Image: dockerhub.kubekey.local/prom/alertmanager:v0.21.0
Image ID: docker-pullable://dockerhub.kubekey.local/prom/alertmanager@sha256:913293083cb14085bfc01018bb30d1dcbbc9ed197ae21ef2ca917b0d29265198
Ports: 9093/TCP, 9094/TCP, 9094/UDP
Host Ports: 0/TCP, 0/TCP, 0/UDP
Args:
–config.file=/etc/alertmanager/config/alertmanager.yaml
–storage.path=/alertmanager
–data.retention=120h
–cluster.listen-address=[$(POD_IP)]:9094
–web.listen-address=:9093
–web.route-prefix=/
–cluster.peer=alertmanager-main-0.alertmanager-operated.kubesphere-monitoring-system.svc:9094
–cluster.peer=alertmanager-main-1.alertmanager-operated.kubesphere-monitoring-system.svc:9094
–cluster.peer=alertmanager-main-2.alertmanager-operated.kubesphere-monitoring-system.svc:9094
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Message: level=info ts=2021-03-05T02:55:03.591Z caller=main.go:216 msg=“Starting Alertmanager” version=“(version=0.21.0, branch=HEAD, revision=4c6c03ebfe21009c546e4d1e9b92c371d67c021d)”
level=info ts=2021-03-05T02:55:03.591Z caller=main.go:217 build_context=“(go=go1.14.4, user=root@dee35927357f, date=20200617-08:54:02)”
Exit Code: 2
Started: Fri, 05 Mar 2021 10:55:02 +0800
Finished: Fri, 05 Mar 2021 10:56:38 +0800
Ready: False