> _and_ can't re-create the cluster with a new version every time actually I used kubeadm and the higher the version was going the better it worked for major u

> _and_ can't re-create the cluster with a new version every time actually I used kubeadm and the higher the version was going the better it worked for major upgrades. At the moment with the new master upgrade methods I did not have any problems so far. on two clusters. Sadly I created my cluster with an "external" etcd, beside that it is internal and also tried to maintain my own certificates, which is now a pita. (at the time cert handling wasn't as good in kubeadm as it is now). Also I have a CloudConfig/Ignition Config creator which can bootstrap all necessary configs to bootstrap a kubeadm cluster on ContainerLinux/Flatcar Linux. So if I really have time I can just recreate a new cluster and move everything over. (I.e. the only thing which is problematic in "moving" over is the database created with kubedb) Also you can use keepalived as your kubeadm load balancer.