-
Notifications
You must be signed in to change notification settings - Fork 260
fix: set logger for controller-runtime #4123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: GitHub <[email protected]>
|
/azp run Azure Container Networking PR |
|
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR injects the zap logger into controller-runtime's global logging infrastructure to ensure internal machinery logs are properly captured and formatted. The change enables controller-runtime's internal operations to use the application's configured zap logger instead of the default logger.
- Adds the controller-runtime log package import
- Sets the global controller-runtime logger to use the application's zap logger via zapr adapter
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
injects the zap logger into controller-runtime so that internal machinery logs work