From 43765101f5c4e53b663243b53d9997ff819fca62 Mon Sep 17 00:00:00 2001 From: Joakim Olsson Date: Tue, 19 May 2026 05:13:51 +0000 Subject: [PATCH] fix(k8s): point OTEL endpoint to k8s-monitoring-alloy service (#839) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The receiver suffix was stale — the `grafana-k8s-monitoring` module deploys a single Service named `k8s-monitoring-alloy` in the `monitoring` namespace, not `k8s-monitoring-alloy-receiver`. Pods were failing to ship traces with: ``` dial tcp: lookup k8s-monitoring-alloy-receiver.monitoring.svc.cluster.local on 100.64.0.10:53: no such host ``` Drop the `-receiver` suffix so the OTLP exporter resolves the correct service. Reviewed-on: https://gitea.unbound.se/unboundsoftware/schemas/pulls/839 --- k8s/deploy.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/k8s/deploy.yaml b/k8s/deploy.yaml index 7c55136..5fc51f2 100644 --- a/k8s/deploy.yaml +++ b/k8s/deploy.yaml @@ -67,7 +67,7 @@ spec: containerPort: 8080 env: - name: OTEL_EXPORTER_OTLP_ENDPOINT - value: http://k8s-monitoring-alloy-receiver.monitoring.svc.cluster.local:4318 + value: http://k8s-monitoring-alloy.monitoring.svc.cluster.local:4318 envFrom: - configMapRef: name: schemas