Config master redundancy


I don’t know if Icingadb and latest version provides this redundancy?

If not. how do you ensure you have it so you can bring the redundant node up when the active nodes goes down?


how did you manage it previously?

As I can remember in this book it is mentioned that there should only be one config master. If it’s dead, fix it or promote a secondary master node and remove the old one from the config.

If you bring a new one up, forget the old one.

Currently I use Git.

Do you know a proper procedure to promote the secondary master as config master in case the config master goes down?