This message was deleted.

in theory you could just swap in the 0.61.1 operator assuming all of the values are the same/still supported since 0.59.1 by replacing the image. I believe rancher does the mirroring of the upstream so they can keep a strict version control in place as they technically have to support the monitoring service as part of the rancher support package.

image:
    repository: rancher/mirrored-prometheus-operator-prometheus-operator
    tag: v0.59.1

prometheusConfigReloader:
    image:
      repository: rancher/mirrored-prometheus-operator-prometheus-config-reloader
      tag: v0.59.1

Thanks for that - yes, I was thinking of pointing directly to the newer version & seeing what happens, may be my only option at this point.

https://github.com/rancher/image-mirror link to my reference about how rancher does upstream mirroring

Managed to update the images that were being used via the chart YAML, but now struggling to get the Alertmanager spec updated. Trying to apply alertmanagerconfigmatchstrategy via the chart YAML too, so a namespace isn't enforced for my AlerrtmanagerConfig routes (deployed via CRD). But that config isn't being applied. Have also tried updating the Alertmanager CRD with it, but again not working. Any tips would be appreciated!