You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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?
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!
The text was updated successfully, but these errors were encountered: