Repository-Metriken
- Stars
- (122.268 Stars)
- PR-Merge-Metriken
- (Durchschn. Merge 28T 17h) (343 gemergte PRs in 30 T)
Beschreibung
What would you like to be added?
Before introduction of Beta metric stability, we had many important metrics that were stuck in Alpha state.
Would like to propose a list of metric candidates that should be reviewed for graduation to Beta.
We would still review each metric individually for any antipattern, but fact they are in use for so long should be good enough reason for graduation.
Graduation criteria are at https://github.com/kubernetes/community/blob/9de615daee15bdee370a825dc0ef150eac189700/contributors/devel/sig-instrumentation/metric-instrumentation.md#graduating-to-beta
Subtasks:
- https://github.com/kubernetes/kubernetes/issues/136304
- https://github.com/kubernetes/kubernetes/issues/136305
- https://github.com/kubernetes/kubernetes/issues/136306
- https://github.com/kubernetes/kubernetes/issues/136307
- https://github.com/kubernetes/kubernetes/issues/136308
- https://github.com/kubernetes/kubernetes/issues/136310
- https://github.com/kubernetes/kubernetes/issues/136311
- https://github.com/kubernetes/kubernetes/issues/136312
- https://github.com/kubernetes/kubernetes/issues/136313
Why is this needed?
Those metrics have been already present in K8s for long time and are at use by GKE.
While we won't necessarily want to graduate them GA, marking them as Beta would indicate their importance and allow community to pay more attention to them over other Alpha metrics.
/cc @richabanker @dgrisonnet