![]() While `ClusterStatus` will be maintained and uploaded, it won't be used by the internal `kubeadm` logic in order to determine the etcd endpoints anymore. The only exception is during the first upgrade cycle (`kubeadm upgrade apply`, `kubeadm upgrade node`), in which we will fallback to the ClusterStatus to let the upgrade path add the required annotations to the newly created static pods. |
||
---|---|---|
.. | ||
BUILD | ||
cluster_status.go | ||
configmap.go | ||
pods.go |