kubeadm reset clean up iptables?

771 views

Skip to first unread message

Kenny Ho

unread,

Feb 8, 2017, 2:30:21 PM2/8/17

to kubernetes-sig-cluster-lifecycle

Hi,

Is kubeadm reset suppose to clean up the changes it made to the iptables? I am trying to bring up a cluster with kubeadm using flannel but I am having trouble getting the container to access the internet. I think at one point I could ping 8.8.8.8 but that seems to have stopped working after I did a reset (and I am all confused now.) The only thing I seems to be able to ping is the host node IP of the specific container. Can someone point me to the right direction?

Regards,

Kenny

Kenny Ho

unread,

Feb 9, 2017, 2:21:39 PM2/9/17

to kubernetes-sig-cluster-lifecycle

Ok, I just want to give some feedback. Looks like kubeadm reset doesn't quite reset everything due to the stateful nature of some of the networking config. I did a reset and even reinstalled docker-engine and kube* and I still see 3 nodes via calicoctl before I join any nodes to my new cluster. (I have tried canal and calico network after I fail to get flannel working.) May be this is because all the networking config uses hostPath. I am not sure if a kubectl delete -f will clean those up but I will give that a try.