libcluster

Backs Act 1: you don’t want to hardcode node lists.

Questions to answer

• What a strategy is: the behaviour, and what it calls once it has a node list.
• Per strategy — Epmd, Gossip, DNSPoll, Kubernetes — how it discovers peers and what it assumes about the network.
• How libcluster connects and disconnects — does it go through net_kernel, and what happens on failure?
• Which strategy NETZlive uses, and why.
• The claim “configuration is the only thing that changes between strategies” — true, or does application code ever notice?

Where the evidence lives

• libcluster/lib/cluster/strategy.ex and the per-strategy modules. Pin the version.
• NETZlive’s libcluster config — see NETZlive in production.