Rostislav M. Georgiev 5d0127493c kubeadm upgrade plan: don't load component configs ...

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 <rostislavg@vmware.com>

2020-06-10 14:23:53 +03:00

..

strict

Run hack/update-vendor.sh

2020-05-16 07:54:33 -04:00

testdata

kube-proxy: add '--bind-address-hard-fail' flag to treat failure to bind to a port as fatal

2020-04-02 13:13:10 +08:00

BUILD

Run hack/update-vendor.sh

2020-05-16 07:54:33 -04:00

cluster_test.go

kubeadm upgrade plan: don't load component configs

2020-06-10 14:23:53 +03:00

cluster.go

kubeadm upgrade plan: don't load component configs

2020-06-10 14:23:53 +03:00

common_test.go

Initial deprecation of kubeadm v1beta1 apis

2019-10-06 23:26:12 +00:00

common.go

switch over k/k to use klog v2

2020-05-16 07:54:27 -04:00

initconfiguration_test.go

kubeadm: remove commented test

2019-10-24 22:58:01 +03:00

initconfiguration.go

switch over k/k to use klog v2

2020-05-16 07:54:27 -04:00

joinconfiguration_test.go

Initial deprecation of kubeadm v1beta1 apis

2019-10-06 23:26:12 +00:00

joinconfiguration.go

switch over k/k to use klog v2

2020-05-16 07:54:27 -04:00