Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add explanation for setup #48

Open
lieberlois opened this issue Aug 27, 2023 · 2 comments
Open

Add explanation for setup #48

lieberlois opened this issue Aug 27, 2023 · 2 comments

Comments

@lieberlois
Copy link

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!

@lieberlois
Copy link
Author

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?

@zawachte
Copy link
Collaborator

zawachte commented Sep 6, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants