Standardize goroutine leak detection

[bhope]

We can consider designing a strategy to detect and address goroutine leaks (mem leaks) across KSM

This could help us detect such occurrences: #2867

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

Details

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.

[wasimat404]

/assign

[wasimat404]

After looking more carefully, this needs deeper Go and kube-state-metrics codebase context than I have right now. Unassigning so it stays open for someone better positioned. Thanks for considering!

/unassign