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
There were a number of changes in kubeadm configuration file structure between 1.9 and 1.11 (kubernetes/kubernetes#63788) and 1.11 to 1.12 (kubernetes/kubernetes#65945), because of this changing of k8 version in the source (#162, #197) will not work.
The easiest workaround IMO - to bump apiVersion: kubeadm.k8s.io/v1alpha2, set #162 to 1.11, create cluster and after that apply kubeadm upgrade to 1.12.
The more flexible way may be to templetize master.yaml or to provide different config generator function based on k8 version.
There were a number of changes in kubeadm configuration file structure between 1.9 and 1.11 (kubernetes/kubernetes#63788) and 1.11 to 1.12 (kubernetes/kubernetes#65945), because of this changing of k8 version in the source (#162, #197) will not work.
The easiest workaround IMO - to bump
apiVersion: kubeadm.k8s.io/v1alpha2
, set #162 to 1.11, create cluster and after that apply kubeadm upgrade to 1.12.The more flexible way may be to templetize
master.yaml
or to provide different config generator function based on k8 version.hetzner-kube/pkg/clustermanager/configs.go
Lines 8 to 35 in 034fefa
And the best way will be to support latest and previous stable version of k8s.
The text was updated successfully, but these errors were encountered: