You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Component configs are used by kubeadm upgrade plan at the moment. However, they
can prevent kubeadm upgrade plan from functioning if loading of an unsupported
version of a component config is attempted. For that matter it's best to just
stop loading component configs as part of the kubeadm config load process.
Signed-off-by: Rostislav M. Georgiev <[email protected]>
// FetchInitConfigurationFromCluster fetches configuration from a ConfigMap in the cluster
64
-
funcFetchInitConfigurationFromCluster(client clientset.Interface, w io.Writer, logPrefixstring, newControlPlanebool) (*kubeadmapi.InitConfiguration, error) {
64
+
funcFetchInitConfigurationFromCluster(client clientset.Interface, w io.Writer, logPrefixstring, newControlPlane, skipComponentConfigsbool) (*kubeadmapi.InitConfiguration, error) {
65
65
fmt.Fprintf(w, "[%s] Reading configuration from the cluster...\n", logPrefix)
66
66
fmt.Fprintf(w, "[%s] FYI: You can look at this config file with 'kubectl -n %s get cm %s -oyaml'\n", logPrefix, metav1.NamespaceSystem, constants.KubeadmConfigConfigMap)
0 commit comments