kube_ingress_tls produces duplicate metrics for duplicate Ingress hosts

[mmckeen]

What happened:

For an Ingress with the following spec:

  ingressClassName: external
  rules:
  - host: foo.com
    http:
      paths:
      - foo
  - host: foo.com
    http:
      paths:
      - bar
  tls:
  - hosts:
    - foo.com
    - foo.com
    secretName: foo-secret

kube-state-metrics produces duplicate kube_ingress_tls metrics resulting in Error 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:

• kube-state-metrics version: 2.12.0
• Kubernetes version (use kubectl version): v1.28.13
• Cloud provider or hardware configuration: N/A
• Other info: N/A

[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.

[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