-
Notifications
You must be signed in to change notification settings - Fork 260
fix zap logger rotation issues #2344
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
Conversation
5d76c46 to
24bde54
Compare
24bde54 to
f12fcad
Compare
8746536 to
e535a9a
Compare
|
Can we add more to the description about what the rotation issue is ? |
e535a9a to
30fcb2a
Compare
| var config common.PluginConfig | ||
| config.Version = version | ||
|
|
||
| logDirectory := "" // Sets the current location as log directory |
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.
did we validate ipam logs moved to zap
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.
yes I did with this PR: #2299
Verified azure-ipam.log
30fcb2a to
3280724
Compare
behzad-mir
left a comment
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.
plz make ssure we don't have any "github.com/Azure/azure-container-networking/log in the CNI and network related packages
a3c2692 to
ffb25af
Compare
ffb25af to
e1ad4aa
Compare
Reason for Change:
This PR is to fix log rotation issue that is crashed after windows nodes are restarted.
Issue Fixed:
Requirements:
Notes: