unboundsoftware/schemas
6
0
Fork 0
Code Issues 1 Pull Requests 1 Actions Packages Projects Releases 33 Activity

fix(k8s): point OTEL endpoint to k8s-monitoring-alloy service
schemas / vulnerabilities (pull_request) Successful in 1m57s
Details
schemas / check (pull_request) Successful in 2m37s
Details
schemas / check-release (pull_request) Successful in 3m32s
Details
pre-commit / pre-commit (pull_request) Successful in 5m43s
Details
schemas / build (pull_request) Successful in 5m54s
Details
schemas / deploy-prod (pull_request) Has been skipped
Details

Browse Source 
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.
This commit is contained in:
Joakim Olsson
2026-05-19 07:01:41 +02:00
parent 7dddc70eda
commit f349f6e56f
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
k8s/deploy.yaml
+1 -1
View File
@@ -67,7 +67,7 @@ spec:
containerPort: 8080 containerPort: 8080
env: env:
- name: OTEL_EXPORTER_OTLP_ENDPOINT - 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: envFrom:
- configMapRef: - configMapRef:
name: schemas name: schemas