fix(k8s): point OTEL endpoint to k8s-monitoring-alloy service #839

Merged
argoyle merged 1 commits from fix-otel-endpoint into main 2026-05-19 05:13:52 +00:00

1 Commits

Author SHA1 Message Date
argoyle f349f6e56f fix(k8s): point OTEL endpoint to k8s-monitoring-alloy service
schemas / vulnerabilities (pull_request) Successful in 1m57s
schemas / check (pull_request) Successful in 2m37s
schemas / check-release (pull_request) Successful in 3m32s
pre-commit / pre-commit (pull_request) Successful in 5m43s
schemas / build (pull_request) Successful in 5m54s
schemas / deploy-prod (pull_request) Has been skipped
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.
2026-05-19 07:01:41 +02:00