João Salavessa

Sorry, can't see any logical test fitting in for this fix. The problem is that values from the same object (`ZuulProperties.ignoredPatterns`) and whithin the same flow are being checked against...

For what's worth: after adding `enable_stat_watcher false` back in March (as mentioned by @ashie [here](#issuecomment-1070134576)) none of my 120+ servers experienced this issue again.

Hi, Just to add that I also experienced this issue on all my servers which run with `GF_UNIFIED_ALERTING_ENABLED=false`. Can also confirm that everything works fine in `9.1.8`, the issue started...

@armandgrillet - yes we are (the default for the official docker image under `/var/lib/grafana/grafana.db`).

Could it be related to [#121437](https://github.com/kubernetes/k8s.io/issues/6010)? I've been facing issues with kubernetes 1.27.7 because kubectl binary seems to be unavailable from at least one CDN location.

@teocns Not sure if I understand your comment but the issue is not related with the actual node type, that works just fine. The issue is that the **label** (at...

> Repeats of an existing notification will get the same annotation thus the same image. We would have to update the annotation. We do not want the ruler to take...

Hi @grobinson-grafana, That would definitely work and, as I see it, it's better by a million miles than the current behavior where we can have an alert being fired for...

Hi @justinsb Every time we perform a kops operation which "overwrites" the cluster's server endpoint in the local `~/.kube/config` (e.g. `kops update cluster --name= --yes` or `kops export kubecfg --name=...

Hi @justinsb 👋 I didn't go deep enough testing kOps or looking into the source code to be able to tell if `cluster.Spec.API.PublicName` works for us without having any other...