Open ZhangsongLee opened 9 months ago
Could you try KSM v2.8.2?
There are some big changes around CRD after v2.8.2.
But I used commit(https://github.com/kubernetes/kube-state-metrics/commit/eac6d3b1c994bd7dbd76026188d2b374bf000f20) after v2.8.2
v2.8.2+ has some bugs, you can find them in issues.
I guess this might be related as well.
Is v2.8.2 working for you?
Unfortunately, v2.8.2 is not working :(
#HELP #TYPE
now appears, but still no metrics
HELP kube_customresource_custom_request_cpu request cpu metrics
TYPE kube_customresource_custom_request_cpu gauge
This feature is working in my cluster.
Could you try examples here https://github.com/kubernetes/kube-state-metrics/blob/main/docs/customresourcestate-metrics.md?
I guess user configuration is not correct, you can add logs and rebuild KSM to debug. https://github.com/kubernetes/kube-state-metrics/pull/2299
/assign @CatherineF-dev /triage accepted
Hi @ZhangsongLee, is this issue resolved or not?
What happened:
There is a issues when a CRD is not applied before starting ksm
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Used Configuration:
Anything else we need to know?: I found a related issue https://github.com/kubernetes/kube-state-metrics/issues/2142, this issue is before starting ksm, CRD already existed.
Environment: