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
promote apiserver_request_total to STABLE status #99788
Conversation
/sig instrumentation api-machinery |
/priority important-soon |
d6b5ee3
to
355f321
Compare
/retest |
1 similar comment
/retest |
We've dropped the content-type field since it is effectively unbounded (we had a sec-vuln about this before actually). We retain all other fields, despite their unboundedness due to the fact that we can now explicitly set bounds on label values. Change-Id: Icc483fc6a17ea6382928f4448643cda6f3e21adb
/retest |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lavalamp, 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 |
We've dropped the content-type field since it is effectively unbounded
(we had a sec-vuln about this before actually). We retain all other
fields, despite their unboundedness due to the fact that we can now
explicitly set bounds on label values.
Change-Id: Icc483fc6a17ea6382928f4448643cda6f3e21adb
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This is a common metric used for SLOs/SLIs. We are promoting this to stable status to preserve that intent while shedding less useful dimensions.
Which issue(s) this PR fixes:
Fixes #91536
Special notes for your reviewer:
We went over this in the SIG Api-Machinery meeting and agreed this was appropriate.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: