[regression] /metrics port down when not existing CRD are listed in config file

[bmm-alc]

What happened:
we use https://github.com/fluxcd/flux2-monitoring-example/blob/bcae1ef44963da89caabe962a93280c0dfad3381/monitoring/controllers/kube-prometheus-stack/kube-state-metrics-config.yaml as part of our config for FluxCD, but we didn´t deploy resourcesimagepolicies and imageupdateautomations from apiGroup image.toolkit.fluxcd.io (they are optional and we don't use them).
Before 2.11.0 release it would not cause any problem, except recurring warning messages.

since version 2.11.0, as long as theses resources are listed, the '/metrics' is down from prometheus POV
removing them, brought back the endpoint up in prometheus.

What you expected to happen:
/metrics to be up and running

How to reproduce it (as minimally and precisely as possible):
declaring not deployed resources should trigger the issue.

Anything else we need to know?:

Environment:

• kube-state-metrics version: 2.11.0
• Kubernetes version (use kubectl version): 1.29.1
• Cloud provider or hardware configuration: scaleway

[CatherineF-dev]

Could you provide steps to reproduce this issue?

[bmm-alc]

closing because I don't have time to investigate this

[CatherineF-dev]

Okay, we can keep it open and wait others to provide steps to reproduce. Feel it might be an issue.

/reopen

[k8s-ci-robot]

@CatherineF-dev: Reopened this issue.

In response to this:

Okay, we can keep it open and wait others to provide steps to reproduce. Feel it might be an issue.

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[logicalhan]

/assign @rexagod
/triage accepted

[logicalhan]

/remove-lifecycle rotten