Use kubeadm reset force flag (#21)

This prevents the cluster from starting up with current K8S versions (1.12>= it seems). Otherwise the startup fails with `kubeadm reset` waiting for interactive response.
galexrt · Nov 23, 2018 · 2cc840c · 2cc840c
2 parents c3f6a7b + b1d2155
commit 2cc840c
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/Vagrantfile b/Vagrantfile
@@ -69,7 +69,7 @@ SCRIPT
 $kubeMasterScript = <<SCRIPT
 
 set -x
-kubeadm reset
+kubeadm reset -f
 kubeadm init #{KUBEADM_INIT_FLAGS} \
     --apiserver-advertise-address=#{MASTER_IP} \
     --pod-network-cidr=#{POD_NW_CIDR} \

diff --git a/Vagrantfile_nodes b/Vagrantfile_nodes
@@ -68,7 +68,7 @@ SCRIPT
 $kubeMinionScript = <<SCRIPT
 
 set -x
-kubeadm reset
+kubeadm reset -f
 
 if [ -n "#{KUBEADM_JOIN_FLAGS}" ]; then
     kubeadm join \