CatherineF-dev

Okay. I guess the crash might be related to https://github.com/kubernetes/kube-state-metrics/issues/2202 Discussed with @logicalhan yesterday around moving CustomResourceStateMetrics feature out of KSM repo. This issue is one datapoint which supports this...

/triage accepted

However, it's a stable metric stated in https://github.com/kubernetes/kube-state-metrics/blob/main/docs/deployment-metrics.md Any ideas for this case? Should we introduce a new metric? cc @dgrisonnet

Got it. Created https://github.com/kubernetes/kube-state-metrics/issues/1995 and https://github.com/kubernetes/kube-state-metrics/pull/1996 to discuss definitions of `stable metrics` in kube-state-metrics repo.

TLDR: we can add new labels for KSM stable metric. cc @augustfengd Feel free to add a new label if you're available.

I think we can split it into kube-state-metrics and kube-state-metrics-operator in the future if it's needed. Because 1. It's a breaking change (users need to deploy kube-state-metrics-operator) and needs to...

> Could you elaborate why you think kube-state-metrics-operator is a breaking change to kube-state-metrics? I thought `KubeStateMetrics, which sets up new instances of kube-state-metrics` is related to auto-scaling, which will...

Okay, I think both KubeStateMetrics and auto-sharding should be moved into kube-state-metrics-operator. So that kube-state-metrics-operator responsibility is managing pods. CustomResourceMonitor is similar with other metrics, which maybe can be kept...

/assign

1. discovery imports many packages, which is similar to app package. Will move this under app. 2. util are highly coupled with custom resource state feature. Will move this under...