-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
🐛 don't override global log in builder #1911
🐛 don't override global log in builder #1911
Conversation
The recent change kubernetes-sigs@598978c#diff-e77b9468ab935d5ea4d5cdae3b994114bada17df0001570e4b1436419afd50ccR312 introduced a bug by overriding `log` with the log created by a builder, resulting in all logs produced by `controller-runtime` having `controller`, `controllerGroup` and `controllerKind` set to the last created controller.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alvaroaleman, k8s-infra-cherrypick-robot The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Any plans to release a bugfix release of the v0.12 release branch? This is currently messing up our logs. |
+1 would be nice to have a v0.12.2 release. |
controller runtime v0.12.1 had issues in which, controller logging format was overwritten with last caller Name/Value. Please refer to PR kubernetes-sigs/controller-runtime#1911 Signed-off-by: Rahul Jain <[email protected]>
controller runtime v0.12.1 had issues in which, controller logging format was overwritten with last caller Name/Value. Please refer to PR kubernetes-sigs/controller-runtime#1911 Signed-off-by: Rahul Jain <[email protected]>
controller runtime v0.12.1 had issues in which, controller logging format was overwritten with last caller Name/Value. Please refer to PR kubernetes-sigs/controller-runtime#1911 Signed-off-by: Rahul Jain <[email protected]>
kubernetes-sigs/controller-runtime#1911 This was causing all controllers to log from the slice controller logger.
This is an automated cherry-pick of #1907
/assign alvaroaleman