When an Ingress resource is deleted, its corresponding metrics remain in Prometheus and are not cleaned up automatically.

[tengxunchao]

Environment：
Kubernetes version: 1.24.17
nginx-ingress version: v1.12.1

Problem
When an Ingress resource is deleted, its corresponding metrics remain in Prometheus and are not cleaned up automatically. These stale metrics only disappear after restarting the nginx-ingress controller.

Question
Is there a way to ensure that these metrics are no longer exposed to Prometheus without restarting nginx-ingress?
Are there any configuration options in nginx-ingress to optimize this behavior?
Or, is there a better recommended approach for handling stale Ingress metrics?

The Ingress corresponding to sit-prometest22.sss.cn in the picture has already been deleted, but Prometheus is still scraping metrics related to it.

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines 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.

[frittentheke]

Likely related / duplicate of this one #10242