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
add container probe duration metrics #104484
add container probe duration metrics #104484
Conversation
@SergeyKanzhelev how does this look as a draft change for probe duration metrics? are we on the right track? |
c7f256e
to
c837bb9
Compare
/triage accepted Could you update the proper unit tests for the new feature? Also, I'm not 100% sure on this, but it looks like the jobs are flaking. Rerunning them... |
Also, please edit the section Does this PR introduce a user-facing change?, since it does introduce a new change. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@pacoxu: /release-note-edit must be used with a release note block. In response to this:
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. |
/release-note-edit
|
/sig instrumentation |
@@ -474,3 +475,50 @@ func TestStartupProbeDisabledByStarted(t *testing.T) { | |||
expectContinue(t, w, w.doProbe(), msg) | |||
expectResult(t, w, results.Success, msg) | |||
} | |||
|
|||
func TestGetPodLabelName(t *testing.T) { |
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.
@dgrisonnet thx for the continual feedback!
Does the below set of cases prove out everything we want?
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.
gentle ping @dgrisonnet @SergeyKanzhelev
This PR is ready for another "consider for merge" review
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.
The new changes looks good from my side, but I would love to have a second pair of eyes on these assumptions: #104484 (comment)
/assign |
gentle ping @pacoxu thank you! |
I did some testing. Here are four examples including static pod and general pods.
The metrics for pods above
|
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
@SergeyKanzhelev can we merge this? |
@SergeyKanzhelev @pacoxu @dgrisonnet should we take advantage of the beginning of the 1.25 cycle and add this to the milestone and merge? |
kindly ping @dgrisonnet |
I somehow missed the pings, sorry about that. I think this PR is good to go now that my initial concerns have been addressed. /unhold |
gentle ping @mrunalp |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dashpole, jackfrancis, logicalhan, mrunalp, SergeyKanzhelev 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 feature
What this PR does / why we need it:
This PR adds duration metrics for kubelet container probes.
Which issue(s) this PR fixes:
Fixes #101035
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: