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
matchCondition metrics for beta graduation #119311
Conversation
Skipping CI for Draft Pull Request. |
@ivelichkovich: GitHub didn't allow me to assign the following users: a_sykim. Note that only kubernetes members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. 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. |
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
Subsystem: subsystem, | ||
Name: "match_condition_evaluation_seconds", | ||
Help: "Admission match condition evaluation time in seconds, identified by name and broken out for each kind containing matchConditions (webhook or policy), operation and type (validate or admit).", | ||
Buckets: []float64{0.001, 0.005, 0.01, 0.025, 0.1, 0.2, 0.25}, |
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.
Per our discusson slack, the buckets need to be updated
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 I already updated with this commit, do you think they need even more granular? f3b8a4b
Help: "Admission match condition evaluation exclusions count, identified by name of resource containing the match condition and broken out for each kind containing matchConditions (webhook or policy), operation and admission type (validate or admit).", | ||
StabilityLevel: metrics.ALPHA, | ||
}, | ||
[]string{"name", "kind", "type", "operation"}) |
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 feel like I'm going to get confused between kind/type later on but that might just be me. I don't have a better recommendation on the naming here though 🤔
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 I was having trouble with this too
LGTM label has been added. Git tree hash: 1c0679caef9c4a83cb50956763cbb05a92c87079
|
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.
From instrumentation lgtm
/lgtm
/approve
LGTM label has been added. Git tree hash: cb1228b851297c644f87408f6140ea1b024de1b3
|
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
LGTM label has been added. Git tree hash: 795a09074ce1ab8ca63ff444916d8265b825d30d
|
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ivelichkovich, jpbetz, logicalhan 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 |
/triage accepted |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Adds metrics for beta graduation of https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/3716-admission-webhook-match-conditions
Special notes for your reviewer:
matcher is shared by validatingadmissionpolicies and webhooks so it has to handle emitting both metrics, chose to use label to determine if it's policy or webhook.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: