Metric cardinality enforcement

[ehashman]

Enhancement Description

• One-line enhancement description (can be used as a release note): Dynamically configure allowlists for metric label values at runtime
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2305-metrics-cardinality-enforcement
• Discussion Link: https://github.com/kubernetes/community/blob/master/sig-instrumentation/archive/meeting-notes-2020.md#agenda-2020-04-02
• Primary contact (assignee): @logicalhan @YoyinZyc
• Responsible SIGs: /sig instrumentation
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.21
  • Beta release target (x.y): 1.28-1.29
  • Stable release target (x.y): 1.31
• Alpha
  • KEP (k/enhancements) update PR(s):
    • expand on GA requirements for metrics stability framework #2431
    • Update the metric cardinality kep #2468
  • Code (k/k) update PR(s):
    • Metric cardinality enforcement kubernetes#99385
  • Docs (k/website) update PR(s):
    • Update doc for metric cardinality and disabled metric website#27069
• Beta
  • KEP (k/enhancements) update PR(s):
    • 1.28 KEP-2305: Metric cardinality enforcement #4039
  • Code (k/k) update PR(s):
    • 1.29 KEP-2305: introduce allow-metric-labels-manifest kubernetes#118299
  • Docs (k/website) update(s):
    • 1.29 Document dynamic cardinality enforcement (KEP 2305) website#41998
• Stable
  • KEP (k/enhancements) update PR(s):
    • 1.30 GA Metrics Cardinality Enforcement #4422
    • 1.30 Metrics Cardinality Enforcement - Update README  #4499
    • 1.31 Update latest-milestone for KEP-2305 #4695
  • Code (k/k) update PR(s):
  • Docs (k/website) update(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[ehashman]

/sig instrumentation
/stage alpha

[lilic]

@ehashman is there any action items for either Han or me? Thank you!

[ehashman]

@lilic this KEP graduated to alpha last cycle (1.20), it would be good to finish up beta and graduation criteria and target releases for those.

[ehashman]

@lilic @logicalhan once we have beta/graduation criteria we should decide how we want to target milestones for this moving forward. That's all currently empty:

https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2305-metrics-cardinality-enforcement#post-beta-tasks

[ehashman]

/milestone v1.21

slipped from 1.20

[annajung]

Hi @logicalhan and @lilic, 1.21 Enhancements Lead here

For the enhancement to be included in the milestone, it must meet the following criteria:

• [DONE] The KEP must be merged in an implementable state
• The KEP must have test plans
• The KEP must have graduation criteria
• The KEP must have a production readiness review

Please make sure you update the KEP using the latest template.

Also starting 1.21, all KEP must include a production readiness review. Please make sure to take a look at the instructions and update the KEP to include this. For PRR review, please make sure to reach out to #prod-readiness slack channel asap to get this in before the enhancements freeze coming up on Feb. 9th.

Thank you!

[JamesLaverack]

Hey @logicalhan and @lilic, 1.21 enhancements shadow here,

Just to add to Anna's comment above — enhancement's freeze is 2 days away, Feb 9th EOD PST. Any enhancements that do not complete the requirements in Anna's comment above by the freeze will require an exception.

[ehashman]

I've pinged @logicalhan about getting this added today.