The reload should happen automatically. The reason we haven't added the Alertmanager configuration itself to the CRD is because we see similar collaboration potential with Alertmanager route configurations and receivers as there is with ServiceMonitors. As in each namespace should be able to specify these for themselves.

Thanks for the reply :)
Yes, the reload occurs whenever the secret is updated
You mean we should consider abstracting route and receivers as servicemonitor does?

Yes exactly. It'll be some time, but we already have some of this work planned.

Great! The route is kind of recursive, it's a bit complex.
Break the big alert config into smaller parts is a good idea 👍
I have been thinking to add more to alert crd , it's a good path to go.

I would like to see this happen and would be willing to help out... would we first want to see schema, before we start working on code?

Yes defining a schema in advance would be good, feel free to write up initial outline so we have something to start with. Thanks!

cc @simonpasquier

There are multiple discussions happening around this, I think we need to start deduplicating (#2927, #1528).

Hello! I've started a design document:
https://docs.google.com/document/d/1aVVttvocop8zNezwrNFbHh_HKRW_fhJUZqhmrr8fGK0/edit?usp=sharing

Feel free to comment there...

@simonpasquier That's great! Will take a look at this!

Closed by #3451