From 2aa64246f10b54f4870d4346872e4e41229ad100 Mon Sep 17 00:00:00 2001 From: Joakim Olsson Date: Sat, 17 Oct 2026 11:08:05 +0200 Subject: [PATCH] chore(k8s): send OTLP straight to the Frostmoln Alloy receiver The AWS-era endpoint (k8s-monitoring-alloy*.monitoring) only resolves through an ExternalName alias the Frostmoln observability agent keeps for the migration; point at alloy-logs.observability directly so the alias can go. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01H6eVuR4Yt3m7TbDTDwyZJi --- k8s/deploy.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/k8s/deploy.yaml b/k8s/deploy.yaml index 26d8cc0..6c842a3 100644 --- a/k8s/deploy.yaml +++ b/k8s/deploy.yaml @@ -78,7 +78,7 @@ spec: containerPort: 8080 env: - name: OTEL_EXPORTER_OTLP_ENDPOINT - value: http://k8s-monitoring-alloy.monitoring.svc.cluster.local:4318 + value: http://alloy-logs.observability.svc.cluster.local:4318 envFrom: - configMapRef: name: schemas -- 2.54.0