Pasi Juurikas
Pasi Juurikas
We are observing this same thing happening with our Alloy and self-hosted Mimir.
I'm not using clustering, and there is only one Alloy instance having 2 separate mimir.rules.kubernetes configured. Alloy v1.1.1 in use. The Mimir ruler logs have these kind of things: >...
As I already mentioned, I only have 1 Alloy running non-clustered, but adding a different "mimir_namespace_prefix" to all the "mimir.rules.kubernetes" blocks gets rid of the constant delete/recreate cycle. Thanks @56quarters...