kvass如何和prometheus-operator整合。
aoliang opened this issue · 4 comments
prometheus-operator和kvass有些功能有冲突。比如部署prometheus方式上。
保留prometheus-operator的原因是保留其中很多功能,比如serviceMonitor服务发现方式等。
有同样的需求,thanos是基于prometheus-operator部署的,kvass好像无法融合进来
https://github.com/lilocon/prometheus-community-helm-charts/tree/kvass-integration
我基于社区helm-chart做了一个整合方案,可以参考一下
kvass如何和prometheus-operator整合, 整合有发现至少在配置上是有冲突的。有相关的实践吗? 具体错误日志如下:
time="2022-07-19T09:35:23Z" level=warning msg="config of prometheus-k8s-2 is not up to date, expect md5 = 3302520058018015149, shard md5 = 1278952191560573363" component=coordinator
time="2022-07-19T09:35:23Z" level=warning msg="config of prometheus-k8s-4 is not up to date, expect md5 = 3302520058018015149, shard md5 = 1278952191560573363" component=coordinator
time="2022-07-19T09:35:23Z" level=warning msg="config of prometheus-k8s-3 is not up to date, expect md5 = 3302520058018015149, shard md5 = 1278952191560573363" component=coordinator
time="2022-07-19T09:35:23Z" level=warning msg="config of prometheus-k8s-0 is not up to date, expect md5 = 3302520058018015149, shard md5 = 1278952191560573363" component=coordinator
time="2022-07-19T09:35:23Z" level=warning msg="config of prometheus-k8s-1 is not up to date, expect md5 = 3302520058018015149, shard md5 = 1278952191560573363" component=coordinator
time="2022-07-19T09:35:23Z" level=warning msg="shard group prometheus-k8s-0 is unHealth, skip apply change" component=coordinator
time="2022-07-19T09:35:23Z" level=warning msg="shard group prometheus-k8s-1 is unHealth, skip apply change" component=coordinator
time="2022-07-19T09:35:23Z" level=warning msg="shard group prometheus-k8s-2 is unHealth, skip apply change" component=coordinator
time="2022-07-19T09:35:23Z" level=warning msg="shard group prometheus-k8s-3 is unHealth, skip apply change" component=coordinator
time="2022-07-19T09:35:23Z" level=warning msg="shard group prometheus-k8s-4 is unHealth, skip apply change" component=coordinator