Open mmckeen opened 2 weeks ago
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.
What happened:
For an Ingress with the following spec:
kube-state-metrics
produces duplicatekube_ingress_tls
metrics resulting inError on ingesting samples with different value but same timestamp
errors when Prometheus scrapes these metrics.What you expected to happen:
Only a single metric is produced and kube-state-metrics de-duplicates on the
tls_host
label.How to reproduce it (as minimally and precisely as possible):
See above.
Anything else we need to know?:
N/A
Environment:
kubectl version
): v1.28.13