alertmanager/cluster
Povilas Versockas 7f34cb4716 cluster: Add cluster peers DNS refresh job (#1428)
Adds a job which runs periodically and refreshes cluster.peer dns records.

The problem is that when you restart all of the alertmanager instances in an environment like Kubernetes, DNS may contain old alertmanager instance IPs, but on startup (when Join() happens) none of the new instance IPs. As at the start DNS is not empty resolvePeers waitIfEmpty=true, will return and "islands" of 1 alertmanager instances will form.

Signed-off-by: Povilas Versockas <p.versockas@gmail.com>
2018-11-23 09:47:13 +01:00
..
clusterpb *: move to memberlist for clustering 2018-02-08 12:18:44 +01:00
advertise.go cluster: fail when no private address can be found (#1437) 2018-07-05 22:59:56 +02:00
advertise_test.go cluster: fail when no private address can be found (#1437) 2018-07-05 22:59:56 +02:00
channel.go gossip large messages via SendReliable (#1415) 2018-06-15 13:40:21 +02:00
channel_test.go gossip large messages via SendReliable (#1415) 2018-06-15 13:40:21 +02:00
cluster.go cluster: Add cluster peers DNS refresh job (#1428) 2018-11-23 09:47:13 +01:00
cluster_test.go cluster: skip tests when no private ip address exists (#1470) 2018-08-22 17:40:07 +02:00
delegate.go cluster: make sure we don't miss the first pushPull (#1456) 2018-07-09 11:16:04 +02:00