chore(k8s): send OTLP straight to the Frostmoln Alloy receiver
schemas / check (pull_request) Successful in 1m1s
schemas / vulnerabilities (pull_request) Successful in 42s
schemas / check-release (pull_request) Successful in 1m8s
pre-commit / pre-commit (pull_request) Successful in 1m36s
schemas / build (pull_request) Successful in 1m42s
schemas / deploy-prod-frostmoln (pull_request) Skipped

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 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01H6eVuR4Yt3m7TbDTDwyZJi
This commit is contained in:
argoyleandClaude Opus 5.5 committed 2026-10-17 11:08:05 +02:00
1 parent 93bb89e450
commit 2aa64246f1
1 file changed
+1 -1
+1 -1
View File
@@ -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