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/kubelet/prober to structured logging #99830
Migrate pkg/kubelet/prober to structured logging #99830
Conversation
Hi @krzysiekg. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/sig node |
@@ -193,8 +192,8 @@ func (m *manager) AddPod(pod *v1.Pod) { | |||
if c.LivenessProbe != nil { | |||
key.probeType = liveness | |||
if _, ok := m.workers[key]; ok { | |||
klog.Errorf("Liveness probe already exists! %v - %v", | |||
format.Pod(pod), c.Name) | |||
klog.ErrorS(nil, "Liveness probe already exists for container", |
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.
That 's will be result in
I0102 15:04:05.067890 1234 prober_manager.go:956] "Liveness probe already exists for container"
beacuse err == nil will result in this
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.
@yuzhiquan Problem you are mentioning should be fixed separately to migration. Let's continue with migration as described in migration guide.
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.
@yuzhiquan Problem you are mentioning should be fixed separately to migration. Let's continue with migration as described in migration guide.
Sure.
Structured logging migration part looks good to me. |
/triage accepted |
/sig instrumentation |
9491b5d
to
86b0efc
Compare
/retest |
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.
/lgtm
@serathius I removed changes not related to structured logging migration from this PR. Could you give it a formal lgtm label? |
/assign @klueska |
@krzysiekg Yes, LGTM |
/milestone v1.21 |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: krzysiekg, mrunalp 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 |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Migrate pkg/kubelet/prober to structured logging
Which issue(s) this PR fixes:
Ref #98976
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: