prometheus push scraping mechanism doesn't work when I have several tenants configured

[JCL38-ORANGE]

Expected Behavior

when I have several tenants (for example tenant A and tenant B) managed by the minio operator I expect to find a minio-prom-additional-scrape-config secret generated with tenants A and B (in order to consult metrics for all my tenants)

Current Behavior

minio-prom-additional-scrape-config secret is generated randomly (either with scraping of tenant A, either with scraping of tenant B).

Steps to Reproduce (for bugs)

1.Install minio operator
2.Configure two tenants with prometheus enabled
3.Delete generated minio-prom-additional-scrape-config secret
4.Check that the generated secret contains either tenant A scraping either tenant B scraping

Your Environment

• Version used (minio-operator): 5.0.17
• Environment name and version (e.g. kubernetes v1.17.2): v1.30.11+k3s1

[JCL38-ORANGE]

Hello,
Any news on this point ?
Thanks and regards,
Jean-Christophe.

[nogweii]

I'm running into the same issue, though slightly differently: I have two tenants configured, one with prometheus scraping and one without. The operator fights with itself, constantly recreating the configuration to scrape and then immediately deleting it.

[JoelRuizRojas]

Hello @JCL38-ORANGE I was able to reproduce this issue, PR #2456 is fixing the issue.