mimir.rules.kubernetes: explicitely mark the component as healthy on …

…successful startup.

If the startup temporarily fails, the component is marked as unhealthy
and the startup is retried indefinitely until it succeeds.
If it succeeds, the component would remain unhealthy.

This change explicitly mark the component as healthy
to fix it.

CHANGELOG.md

@@ -29,6 +29,8 @@ Main (unreleased)
 - Fixed an issue in the `prometheus.exporter.postgres` component that would leak goroutines when the target was not reachable (@dehaansa)
 - Fixed an issue in the `otelcol.exporter.prometheus` component that would set series value incorrectly for stale metrics (@YusifAghalar)
 
+- Fixed an issue in the `mimir.rules.kubernetes` component that would keep the component as unhealthy even when it managed to start after temporary errors (@nicolasvan)
+
 - Fixed issue with reloading configuration and prometheus metrics duplication in `prometheus.write.queue`. (@mattdurham)
 
 - Fixed an issue in the `otelcol.processor.attribute` component where the actions `delete` and `hash` could not be used with the `pattern` argument. (@wildum)

internal/component/mimir/rules/kubernetes/rules.go

@@ -244,6 +244,7 @@ func (c *Component) startupWithRetries(ctx context.Context, leader leadership, s
 			level.Error(c.log).Log("msg", "starting up component failed, will retry", "err", err)
 			health.reportUnhealthy(err)
 		} else {
+			health.reportHealthy()
 			break
 		}
 		startupBackoff.Wait()