DNS Poll - max stable Cluster Size = max DNS Entry Response Count about libcluster HOT 1 OPEN

I'd be open to accepting a PR that makes removing nodes in this strategy optional based on a flag, something like prune: false to disable pruning the node list. I believe there was a reason we actively prune nodes when the source of data for the strategy (e.g. DNS in this case, but could be any system providing service discovery) no longer reports a node as being part of the cluster, but I can't recall the specifics at the moment, but it was a specific choice. libcluster is largely deferring to the source registry to tell us what nodes belong in the cluster. In the case of DNS, it is unusual for a node to disappear from DNS unless it is being permanently removed, but I can imagine scenarios where this might happen, such as under k8s or some other orchestrator that uses DNS for service discovery.

from libcluster.