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
With the switch to v1.10 in #70 we can now make use of kubernetes/kubernetes#55479 and set noTaintMaster: true in kubeadm.conf instead of untainting after initialisation.
+ // Taints specifies the taints the Node API object should be registered with. If this field is unset, i.e. nil, in the `kubeadm init` process
+ // it will be defaulted to []v1.Taint{'node-role.kubernetes.io/master=""'}. If you don't want to taint your master node, set this field to an
+ // empty slice, i.e. `taints: {}` in the YAML file. This field is solely used for Node registration.
+ Taints []v1.Taint
With the switch to v1.10 in #70 we can now make use of kubernetes/kubernetes#55479 and set
noTaintMaster: true
inkubeadm.conf
instead of untainting after initialisation.Perhaps also depends on #71?
The text was updated successfully, but these errors were encountered: