k3s-io/cluster-api-k3s

Add explanation for setup

lieberlois opened this issue · 2 comments

Hi everybody,
I tried to use the k3s bootstrap provider together with the hetzner infrastructure provider. However when using clusterctl generate, the generated manifests used Kubeadm rather than KThrees. Do we need to enable feature flags to use this? Would be great if we could figure this out - I'd be happy to document this in a PR afterwards 🤭

Thanks in advance!

Edit: after having the manifests generated and configured the hetzner provider creates machines and the k3s provider copies some files (e.g. under /etc/rancher/.../config.yaml) but doesnt start up the k3s service. Any ideas?

Can you check the cloudinit logs? /var/log/cloud-init-output.log?