Exception Request: Fix Stable Metric Guideline Violation

[Frederic Branczyk]

Enhancement name: Metrics Stability Enhancement
Enhancement status (alpha/beta/stable): stable
SIG: Instrumentation
k/enhancements repo issue #: https://github.com/kubernetes/enhancements/issues/1209
PR #’s: https://github.com/kubernetes/kubernetes/pull/100082
Additional time needed (in days): 1
Reason this enhancement is critical for this milestone: It's part of the first 3 metrics we're marking as stable and it has a violation of our metrics guidelines.
Risks from adding code late: It's just renaming a metric, I don't expect any risk.
Risks from cutting enhancement: We would be releasing metrics as stable that don't match our own stability guidelines, plus metrics deprecation would take 4 release cycles to fix this.

Best regards,

Frederic

[pal.na...@gmail.com]

Hi Frederic,

Considering that all of the implementation PRs went in before the Code Freeze came into effect and the pending PR is just a fix to guidelines violation, we feel that the risk in getting the PR merged is low. We are APPROVING this exception request and restoring the milestone on the aforementioned PR.

Please do reach out to us on #sig-release of Kubernetes Slack in case you have any questions/comments/concerns.

Best,

Nabarun Pal // Kubernetes 1.21 Release Lead

[Nabarun Pal]

Forwarding my original message, since the Google Groups didn't Reply
to All intended recipients.

--
You received this message because you are subscribed to the Google
Groups "kubernetes-sig-release" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to kubernetes-sig-re...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/kubernetes-sig-release/ee5308ba-d026-4809-aadc-b1afbdb1c1d9n%40googlegroups.com.