There is a bug that can happen sometime, when setting up calico fails because the k8s api-server doesn't accept a connection. I'm not sure what goes wrong though, but I figure maybe we should:
- retry setting up calico if the initial attempt fails
- try to get info about the state of k3s to understand what went wrong
There is a bug that can happen sometime, when setting up calico fails because the k8s api-server doesn't accept a connection. I'm not sure what goes wrong though, but I figure maybe we should: