Duplicate sample for ingress path metrics

[jutley]

What happened:

After upgrading Prometheus to 2.52, we started receiving warnings about duplicate metrics, which were ultimately tied to kube-state-metrics. There are a couple forms of this, most of which area already reported in other tickets (#2405, #2408, #2390), but this is a different variation.

The metric kube_ingress_path is resulting in duplicates. In our case, we do have ingress path entries which are completely redundant (the result of some shoddy helm templates), but it's still a legal Kubernetes state resulting in illegal Prometheus scrape results.

What you expected to happen:

Either the data is de-duplicated, or the duplicates are somehow differentiated (with an index, perhaps).

How to reproduce it (as minimally and precisely as possible):

Create an ingress with duplicate paths, then create metrics for it with kube-state-metrics.

Anything else we need to know?:

Environment:

• kube-state-metrics version: 2.12
• Kubernetes version (use kubectl version): 1.28.9
• Cloud provider or hardware configuration: AWS
• Other info:

[k8s-ci-robot]

This issue is currently awaiting triage.

If kube-state-metrics contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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-sigs/prow repository.

[dgrisonnet]

Closing as a duplicate of #2408.