From a7f4cd76693269cf0cc4d2d00877eb997be20c64 Mon Sep 17 00:00:00 2001 From: Kaitlyn Michael Date: Tue, 3 Jun 2025 13:20:36 -0500 Subject: [PATCH] fix broken links --- .../kubernetes/re-clusters/connect-prometheus-operator.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/operate/kubernetes/re-clusters/connect-prometheus-operator.md b/content/operate/kubernetes/re-clusters/connect-prometheus-operator.md index 324f6f5608..0ca989d726 100644 --- a/content/operate/kubernetes/re-clusters/connect-prometheus-operator.md +++ b/content/operate/kubernetes/re-clusters/connect-prometheus-operator.md @@ -34,7 +34,7 @@ You'll need to configure the following fields to connect Prometheus to Redis Ent | `spec.selector` | `matchLabels` | REC service label (`app: redis.io/service=prom-metrics`) | Apply the file in the same namespace as your Redis Enterprise cluster (REC). - {{}}If Redis Enterprise and Prometheus are deployed in different namespaces, you'll also need to add the [`serviceMonitorNamespaceSelector`](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/api.md#namespaceselector) field to your Prometheus resource. See the [Prometheus operator documentation](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides/getting-started.md#related-resources) for more details on cross-namespace `ServiceMonitor` configuration.{{}} + {{}}If Redis Enterprise and Prometheus are deployed in different namespaces, you'll also need to add the [`serviceMonitorNamespaceSelector`](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/api-reference/api.md) field to your Prometheus resource. See the [Prometheus operator documentation](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides/running-exporters.md) for more details on cross-namespace `ServiceMonitor` configuration.{{}} ```YAML