sidecar: Use zap as logger backend#770
Merged
Merged
Conversation
Madhu-1
reviewed
Feb 17, 2025
Madhu-1
left a comment
Member
There was a problem hiding this comment.
Please update the PR description/commit message to show what exact error you are seeing now without this change.
nixpanic
approved these changes
Feb 17, 2025
Madhu-1
approved these changes
Feb 17, 2025
This patch sets `zap` as logger backend for klog and controller runtime. Signed-off-by: Niraj Yadav <niryadav@redhat.com>
a384931 to
42faeec
Compare
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
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.
This patch sets
zapas logger backend for klogand controller runtime.
Setting the logger is required by controller runtime, not doing so leads to an error in the logs like: