This series tracks alerting, which supports bug 2068601's init-time corruption detection, but: * The initial corruption check keeps the corrupted member from coming up, preventing split-braining. Alerting just lets you know if something bad is happening; it doesn't block anything. * The current initial corruption check seems to ignore large divergence [1]. Alerting will complain about any divergence, regardless of size. * Adding a new alert PrometheusRule to existing clusters is an easier mitigating patch than adjusting the etcd-launching configuration. [1]: https://github.com/etcd-io/etcd/issues/13766#issuecomment-1083033017