Files
schemas/k8s
argoyle 43765101f5
Release / release (push) Failing after 51s
schemas / vulnerabilities (push) Successful in 1m48s
schemas / check (push) Successful in 2m31s
schemas / check-release (push) Successful in 3m1s
pre-commit / pre-commit (push) Successful in 6m59s
schemas / build (push) Successful in 13m14s
schemas / deploy-prod (push) Successful in 1m20s
fix(k8s): point OTEL endpoint to k8s-monitoring-alloy service (#839)
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: #839
2026-05-19 05:13:51 +00:00
..
2022-10-09 20:37:48 +02:00
2022-10-09 20:37:48 +02:00