Restore Jaeger tracing regressed in 198cb4b (+ pin tempo/keycloak)#71
Merged
Conversation
Commit 198cb4b (Apr 15 2026) recompiled the Flexible Config from a template that still carried an old Jaeger bug, reverting a 2024 hand-fix (c7eae17) that had only ever been applied to the compiled krakend.json -- never to the template. That broke Jaeger tracing, reverting three values at once: - jaeger host: jaeger -> jaeeger (nonexistent host) - debug_jaeger exporter disable_traces: false -> true - trace_sample_rate: 1 -> 0.5 Restores the original values, fixing them in both the FC template and the compiled krakend.json so a recompile won't revert them again.
- grafana/tempo:latest drifted to 3.x and broke the tempo.yaml schema -> pin to 2.6.0 - keycloak:26.0 crashes with SIGILL on aarch64 (Apple Silicon) -> bump to 26.2
obokaman-com
requested review from
NarcisDavins,
alombarte,
dhontecillas,
kpacha,
taik0,
thedae and
tonipinel
thedae
approved these changes
Jun 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Valik Solorzano (Zebra) sent over this fixes. The tracing one turned out to be a real regression on our side (nice catch!).
Jaeger tracing had quietly broken back in April. Commit 198cb4b recompiled the Flexible Config from a template that still had an old Jaeger bug, undoing a 2024 fix that had only ever been applied to the compiled krakend.json (never the template). It reverted three things at once: the jaeger host (back to the
jaeegertypo), the debug_jaeger exporter (traces disabled), and trace_sample_rate (1 → 0.5). First commit restores all three, this time in the template too, so a recompile won't wipe it again.Second commit pins two images Valik hit on startup: tempo (latest had drifted to 3.x and broke its config) → 2.6.0, and keycloak (26.0 crashes on Apple Silicon) → 26.2.
Thanks Valik!