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 #839

Merged
argoyle merged 1 commits from fix-otel-endpoint into main 2026-05-19 05:13:52 +00:00
Conversation 0 Commits 1 Files Changed 1
+1 -1
argoyle commented 2026-05-19 05:02:22 +00:00
Owner
Copy Link
Copy 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.

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.
argoyle added 1 commit 2026-05-19 05:02:24 +00:00
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
f349f6e56f 
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.
argoyle merged commit 43765101f5 into main 2026-05-19 05:13:52 +00:00
argoyle deleted branch fix-otel-endpoint 2026-05-19 05:13:53 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
dependencies
Pull requests that update a dependency file
 docker
go
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
acctest (Shiny Acctest) argoyle (Joakim Olsson) buildtools (Buildtools) kubernetes (Kubernetes) releaser (Unbound Releaser) renovate (Renovate Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unboundsoftware/schemas#839
Delete Branch "fix-otel-endpoint"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?