-
Notifications
You must be signed in to change notification settings - Fork 94
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
Support contextual logging #259
Support contextual logging #259
Conversation
1884439
to
759efd4
Compare
Makefile
Outdated
# Check contextual logging. | ||
.PHONY: logcheck | ||
test: logcheck | ||
logcheck: | ||
hack/verify-logcheck.sh |
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.
Please use the one from release-tools
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.
@jsafrane Thank you. I changed to use test-logcheck.
759efd4
to
d0ce7e8
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bells17, jsafrane 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 |
/hold cancel |
What type of PR is this?
/kind feature
What this PR does / why we need it:
I've updated the klog functions used within livenessprobe to contextual logging functions, following the guidelines below:
https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/migration-to-structured-logging.md
In a previous PR below, I addressed structured logging, but I realized that I only handled structured logging and did not address contextual logging.
#202
Therefore, in this PR, I have addressed contextual logging.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
make test
ormake logcheck
)Does this PR introduce a user-facing change?: