We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
可以直接配合prometheus-operator使用吗,我们生产环境有很多k8s集群,每个集群里有部署prometheus-operator, 通过一些operator提供的CRD对象,例如prometheus, prometheusRule等管理promethues和报警规则。但现在是单实例的,不想用hashmod, 需要把prometheus采集进行分片,是否能直接上kvass ?
The text was updated successfully, but these errors were encountered:
这个需求我们也有,我感觉直接上是不行的,需要做一些适配方案的对接才行。
Sorry, something went wrong.
我查了下文档:针对上述问题,我们希望设计一种无侵入的集群化方案,它对使用者表现出来的,是一个与原生Prometheus配置文件一致,API兼容,可扩缩容的虚拟Prometheus。
理论上讲,将operator中,启动的prom的镜像,换为这个应该就ok了。
No branches or pull requests
可以直接配合prometheus-operator使用吗,我们生产环境有很多k8s集群,每个集群里有部署prometheus-operator, 通过一些operator提供的CRD对象,例如prometheus, prometheusRule等管理promethues和报警规则。但现在是单实例的,不想用hashmod, 需要把prometheus采集进行分片,是否能直接上kvass ?
The text was updated successfully, but these errors were encountered: