Howdy folks, does anyone know if there's a way to setup an AlertmanagerConfig with a route that isn't limited to one namespace? My actual AlertmanagerConfig doesn't have a matcher for the namespace, but when I look in my actual Alertmanager config, the namespace is added:

Hello, This is the namespace that your alerteManagerConfig is deployed. It will be added automatically when you create an AlertManagerConfig This matcher mean that only the Alerts of the objet that are in the same namespace as the alertemanagercinfig ( vault) will be send.

@rich-electrician-53678 Is that correct? Seems the `alertmanagerConfigMatcherStrategy`flag that fixes this was added in v.061.1 but ranchers mirrored charts are lagging behind and still on v0.59.1? https://github.com/rancher/charts/blob/dev-v2.7/charts/rancher-monitoring/102.0.0%2Bup40.1.2/values.yaml#L2646 https://github.com/prometheus-operator/prometheus-operator/issues/3737#issuecomment-1326667523

Hi, I have tested the method that i'am talking about, it works Well. You juste need to use the alertemanagerconfiguration available in the chart version 102.0.0+up40.1.2 for rancher-monitoring and rancher-monitoring-crd

Thanks, will give it a shot then 👍