-
Notifications
You must be signed in to change notification settings - Fork 47
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
Use JSON logger with ISO8601 time encoder for controller manager #525
Conversation
6179509
to
53415a5
Compare
/reviewed ok-to-test |
53415a5
to
c2560f2
Compare
@unmarshall thanks for your suggestion. I've incorporated it now. PTAL |
/remove needs/cherry-pick |
Do we have a plan to release |
@ishan16696 yes, that's the reason I removed the |
How to categorize this PR?
/area logging
/kind bug
/needs cherry-pick
What this PR does / why we need it:
Recently merged PR #450 bumped controller-runtime version from
v0.10.2
tov0.13.0
, which changed the default logging behavior for the logger provided for the controllers to print epoch timestamps in the logs which are not human-readable, as is pointed out by kubernetes-sigs/controller-runtime#2024.This PR explicitly sets the logger options to use ISO8601 timestamps for the controller logs, as well as switches the logger from dev mode to json mode, ie, structured logging, for better integration with logging stack in production environments.
Which issue(s) this PR fixes:
Fixes partially #524
Special notes for your reviewer:
/cc @unmarshall @rfranzke
Release note: