Closed mirondeldev closed 6 months ago
Hello, it makes sense to me. And it'd be great to have an option to enable periodical reconciliation of prometheus watched objects.
Added new flag for period reconciliation at v0.42.2 release
It accepts duration format, -controller.prometheusCRD.resyncPeriod=10m
.
By default, it's disabled.
@f41gh7 thx, much appreciated
Current behavior of the
vmprometheusconverter
rely on Prometheus CRDcreate
andupdate
events, e.g.: https://github.com/VictoriaMetrics/operator/blob/e261c37dc973154ff71073d7213000421416bd4e/controllers/vmprometheusconverter_controller.go#L86-L88In some cases (like manual or circumstantial deletion of custom resources) it leads to "orphaned"
Prometheus resources
.So, the problem is VictoriaMetrics Operator does not recreate converted VM-resources after ones being deleted
Steps to reproduce
PodMonitor
PodScraper
resourcePodScraper
resource and keep original PrometheusPodMonitor
PodScraper
resource will not be created untilPodMonitor
will be updated or recreatedWould you please consider implementing reconciliation loop for
Prometheus resources
invmprometheusconverter
?