Kubeadm - When reset issued still tries to load a POD about frakti HOT 4 CLOSED

Sure sounds great and will issue PR and contribute

Thanks
DB

from frakti.

@DarkBlaez The log above is normal which is caused by hyperd restart, don't worry.

Also when a kubeadm reset is done, all files in /etc/cni/net.d are removed. This should be noted in the deploy.md just as a warning or note

Definitely, would you like to send a PR for this? It would be awesome to have you as frakti's contributor.

from frakti.

The bigger issue over having to recreate the cni files is more around hyperd per above...

hyperd[1009]: E0524 10:19:59.988202 1009 persist.go:113] Pod[k8s_POD.0_kube-dns-3913472980-2jz1j_kube-system_af1d4552-3f1e-11e7-aeb4-0021ccd48ab5_10cd9672] failed to load sandbox info: leveldb: not found

Not sure why hyperd is trying to load this since a kubeadm reset was issued. This causes a number of problems if re-initializing a kubernetes cluster. The steps to resolve are unclear and thus makes using hyperd/frakti at this stage not viable.

DB

from frakti.

The problem should be fixed now. Closing this one.

@DarkBlaez Feel free to reopen it if you still encounter problems.

from frakti.