fix(tracing): traces are not exposing pod metadata #14684
Merged
Conversation
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
The `linkerd-podinfo` volume wasn't being added to injected pods, thus forbidding traces to expose the workloads metadata. The cause was that the linkerd-control-plane `values.yaml` file declared the entry `proxy.tracing.enabled` whereas the templates were using `proxy.tracing.enable`.
alpeb
changed the title
alpeb
changed the title
sfleen
approved these changes
Nov 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The
linkerd-podinfovolume wasn't being added to injected pods, thus forbidding traces to expose the pod's metadata.The cause was that the linkerd-control-plane
values.yamlfile declared the entryproxy.tracing.enabledwhereas the templates were usingproxy.tracing.enable.