Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
CONSOLE-1523: Switch logging to klog #1862
CONSOLE-1523: Switch logging to klog #1862
Changes from all commits
ee7d72d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
@zherman0 For changes from
log
toklog
, when viewing console logs, how can we differentiate them?On a 4.6 cluster, I see console log is showing:
While on a cluster with changes in this PR, it shows:
How can I know
Flag inactivity-timeout is set to less then 300 seconds and will be ignored!
is printed withklog
?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.
@yapei not sure why we need to differentiate between them?
Since we will be using just
klog
for the backend logging we dont need to differentiate between anything.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.
Agreed, not sure why you need to tell the difference, but the new klog stuff shows the file name and line number
main.go:211
if that helps.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.
Yeah, the line number tells the truth @zherman0
When verifying the bug
Logging is broken due to mix of k8s.io/klog v1 and v2
we need to confirm whether klog v2 is used. So I thought for this PR we may have same verification process which means I need to confirmklog
is used instead of old logging. That's' my thought but maybe I'm wrong @jhadvig @zherman0There 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.
@yapei @spadgett @zherman0 just one thing to notice here. The
console
backend will be using theklog/v1
since we need to updatehelm
pkg if we want to use theklog/v2
. On the other hand theconsole-operator
moved by this PR to using theklog/v2
. This should not do any harm since those are two different binaries.Just want to point out the difference here and also think out loud about the upgrading to
klog/v2
for the console backend binary.The issue with the
helm
is that the release we are using (and the latest as well) is using k8s1.18.0
pkgs version. In order not to have import collisions they need to be on the1.19.2.
, which their master is on currently , they just need to release it.