OpenShift默认监视堆栈和服务网格操作员

发布于 2025-01-29 03:53:03 字数 616 浏览 3 评论 0原文

我正在使用OpenShift v4.6,并且使用启用用户定义的项目使用默认监视堆栈。 显然指出:

自定义Prometheus实例和通过操作员Lifecycle Manager(OLM)安装的Prometheus运算符,如果启用了用户定义的工作负载监控问题。 OpenShift容器平台不支持自定义Prometheus实例。

我现在想安装OpenShift的服务网格操作员,该操作员用于监视网格的东西想要安装新的Prometheus和Grafana实例。这不是违反上述建议吗?我在OpenShift的文档(或其他任何地方)中找不到任何可以澄清这些矛盾信息的内容。实际上,我向前迈进,并启用了Prometheus和Grafana,并安装了操作员,到目前为止,它似乎并没有“引起问题”,但我什至不知道要寻找哪些问题。任何有经验的人吗?

I am using Openshift v4.6 and I use the default monitoring stack with user defined projects enabled. Openshift's documentation clearly states:

Custom Prometheus instances and the Prometheus Operator installed through Operator Lifecycle Manager (OLM) can cause issues with user-defined workload monitoring if it is enabled. Custom Prometheus instances are not supported in OpenShift Container Platform.

I now want to install Openshift's Service Mesh operator which for monitoring the mesh stuff wants to install a new Prometheus and Grafana instance. Doesn't this go against the above suggestion? I couldn't find anything in Openshift's documentation (or anywhere else) that could clarify this conflicting information. I actually moved forward and installed the operator with Prometheus and Grafana enabled and so far it doesn't seem to "cause issues" but I don't even know what issues to look for. Anyone with any experience on this?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

微暖i 2025-02-05 03:53:03

好吧,有两个操作员覆盖相同的API可能是一个问题。

自定义Prometheus实例和Prometheus操作员已安装
通过操作员生命周期经理(OLM)可能会引起问题
用户定义的工作负载监视是否已启用。定制的普罗米修斯
OpenShift容器平台不支持实例。

潜在的CRD覆盖/与不同版本的不兼容是该问题是警告的原因。

K8S的工作方式有局限性,已经注册的API ,您应该部署相同的操作员版本以避免问题。

这更有意义吗?

Well, having two operators overwriting the same APIS can be an issue.

Custom Prometheus instances and the Prometheus Operator installed
through Operator Lifecycle Manager (OLM) can cause issues with
user-defined workload monitoring if it is enabled. Custom Prometheus
instances are not supported in OpenShift Container Platform.

The potential CRD overwrites/incompatibility with a different version is the reason why the issue is a warning.

There are limitations to how K8s works w/ already registered APIs, you should deploy the same Operator version in order to avoid issues.

Does that make more sense?

丘比特射中我 2025-02-05 03:53:03

我已经在环境上安装了服务网格,并部署了多个应用程序,但没有发现需要重新安装Prometheus或Grafana。在使用OpenShift群集随附的默认监视堆栈时,我能够通过Grafana可视化Pods的性能,而没有任何问题。
希望这有帮助!

I have installed Service Mesh on an environment and deployed several apps and did not find the need to reinstall Prometheus or Grafana. While using the default monitoring stack that comes with the OpenShift cluster, I was able to visualize the performance of the pods through Grafana without any issues.
Hope this helps!

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文