Comment 2 for bug 1913227

I can reproduce this easily enough. Deployed with k8s 1.18 and etcd 3.2, then upgraded to k8s 1.19, and etcd started crashing.

There are known issues with etcd 3.2 in Kubernetes[1] so I think the correct action here is to add an upgrade note instructing users to upgrade to etcd 3.4 prior to upgrading to k8s 1.19.

[1]: https://kubernetes.io/docs/tasks/administer-cluster/configure-upgrade-etcd/#known-issue-etcd-client-balancer-with-secure-endpoints