-
Notifications
You must be signed in to change notification settings - Fork 38.6k
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
Migrate pkg/proxy
to contextual logging: Part 1
#122979
Merged
k8s-ci-robot
merged 1 commit into
kubernetes:master
from
fatsheep9146:pkg-proxy-support-contextual-logging
Apr 23, 2024
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
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.
A comment unrelated to context logging: it might be good to catch termination signals in the context. It would make a more graceful termination possible, but then again, it might break something @danwinship ?
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.
I think the big constraint for exiting is that, ideally, we don't want to exit in the middle of
syncProxyRules
, because then we might fail to do some conntrack cleanup, etc. So if we get INT/TERM, and we aren't insidesyncProxyRules
, then we can exit right away, but if we are insidesyncProxyRules
, we should finish and then exit.I don't know what the right way to implement that is.
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.
IMO
context.Background()
here is a bad option. Subsequent calls to klog.FromContext will use the fallback (global) logger, and that may not be what we want. In the future we may want the opportunity to use some customized logger inkube-proxy
, whithout having to change the global logger. I think there should be a "root context" from which all sub-contexts are derived, and as a consequence, a "root logger". @pohly, please comment on this.I propose that
newOptions()
takes a logger as parameter (and is renamed NewOptions->newOptions):Then call "Run()" with a context with this logger set:
I tested this, and in a perfect world, all log-entries should have
"logger": "kube-proxy"
. They don't.