Kubeadm init idempotency #82
Description
I would expect when I run the site playbook for a second time it would leave the kubernetes cluster in its current state.
In its current version the site playbook really removes the existing cluster with kubeadm reset.
Is there any way to run kubeadm init in an idempotent manner? In its current version it throws errors that few resources already exist.