dc70c79a00
In kubeadm etcd join there is a a bug that exists where, if a peer already exists in etcd, it attempts to mitigate by continuing and generating the etcd manifest file. However, this existing "member name" may actually be unset, causing subsequent etcd consistency checks to fail. This change checks if the member name is empty - if it is, it sets the member name to the node name, and resumes.