Properly set log level for hickory_resolver in proxy #12722
Merged
Conversation
This file contains 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
Followup to linkerd/linkerd2-proxy#2872 , where we swapped the trust-dns-resolver with the hickory-resolver dependency. This change updates the default log level setting for the proxy to account for that.
alpeb
force-pushed
the
alpeb/log-hickory-resolver
branch
from
141cb38
to
a377dd1
Compare
olix0r
approved these changes
Jun 14, 2024
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.
Followup to linkerd/linkerd2-proxy#2872 , where we swapped the trust-dns-resolver with the hickory-resolver dependency. This change updates the default log level setting for the proxy to account for that.