Icinga2 HA Setup some questions

Icinga Web Modules Icinga Director
21

No, only one master should have config in the /etc/icinga2/conf.d directory. This is done via commenting the “include recursive conf.d” in /etc/icinga2/icinga2.conf.
But the icinga2 node wizard command will do that when setting the second master up as a satellite at first and then manually promote it to a master (manually editing the zones.conf and copying the ca, it’s in the docs).

The webinterface can point to both instance of icinga, but the Icinga Director must only point to the config master, as @moreamazingnick said.
image

Also do not create/edit endpoints and zones in the Director! It can lead to big problems with config sync. Only add/edit those in the zones.conf files. This goes for masters and satellites, agents hosts can be created via the Directors “Icinga2 Agent” setting.

2 Likes
22

Okay, many thanks for that explanation.

But for what scenario exists that option in the director to edit zones and masters?

23

To be honest I/we used the Director for managing the satellite zones for quite some time without issues. But at some point, probably when our setup grew to a certain size (x+1 satellites), we started experiencing problems.

The problems problems went away after moving the satellite zone & endpoint configuration to the zones.conf files on our masters. Since then I recommend not using the Director for that. For a test setup it most likely will be fine, but if you don’t learn it the “wrong” way, you can’t get used to it :wink:

1 Like