I think in the context of what I think initially motivated this hot
reloading capability, a big win it provides is avoiding having to
bounce your cluster as your certificates near expiry. If not watched
closely you can get yourself into a state where every node in the
cluster's cert expired,
I think it's all part of the same issue and you're not derailing IMO Abe. For
the user Pabbireddy here, the unexpected behavior was not closing internode
connections on that keystore refresh. So ISTM, from a "featureset that would be
nice to have here" perspective, we could theoretically
