My Icinga is working with 2 masters(Icinga01 and Icinga02) and another server running Icingaweb.
If I stop Icinga2.service in Icinga01, once going to
Icinga - Icinga Director - Deployments
I’m getting the below message and the deploys got stuck.
- Director version (System - About): 1.7.2
- Icinga Web 2 version and modules (System - About): 2.7.3
- Icinga 2 version (icinga2 --version): 2.11.4-1
- Operating System and version: Red Hat Enterprise Linux release 8.1 (Ootpa)
- Webserver, PHP versions: 7.2.24
How can we apply load balance to Icinga Masters?
You can not do this, as there would be manual changes needed to failover and failback.
The problem is that by deploying to the system you give it the authoritative copy of the configuration. So if you now deploy to the second master by changing the endpoint in the UI, it will also get an authoritative copy, so you can failover manually. But when the first master now comes back, there are two different authoritative copies which will cause trouble. So you would need to manually remove it from the first master before joining the cluster again or even better clean both, configure back to deploy on the first master and then deploy again as failback.
The other feature that is not ready for automatic failover/failback it the CA which you perhaps will also need in case of a failure.