Hi sig-cluster-lifecycle,
The kubeadm v1beta4 API has been available since v1.31. Recently, based on feedback regarding issue https://github.com/kubernetes/kubeadm/issues/3155, we discovered a missing field in the API that needs to be added. Although beta version APIs are generally not meant to be modified, after discussions with the maintainers, we believe that introducing an optional field EtcdUpgrade into UpgradeConfiguration.Plan is safe, and we are inclined to make this change. Given that upstream users may be working with the kubeadm API snapshot, we strongly recommend updating the snapshot to use the latest kubeadm v1beta4 API. Additionally, users should update to the latest kubeadm API after every Kubernetes release.
We welcome your feedback and suggestions.
PR: https://github.com/kubernetes/kubernetes/pull/130023
Thank you all!