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

Use RKE2 #348

Open
xetys opened this issue Dec 28, 2021 · 0 comments
Open

Use RKE2 #348

xetys opened this issue Dec 28, 2021 · 0 comments

Comments

@xetys
Copy link
Owner

xetys commented Dec 28, 2021

I am currently working on an approach where hetzner-kube is using RKE2 instead of kubeadmin

Why?

When using kubeadmin, there are still a lot of administrative tasks to do on hetzner-kube's side. In the meantime, RKE is managing most parts, such as cert rotation, network stack, and it is upgradable out of the box. In addition, RKE2 is bringing containerd with crictl directly, rather than relying on the hosts packaging situation.

Thus, we don't need to install and pin docker, kubeadm and so on.

Challenges

At the current state, hetzner-kube is capable of several options, such as phase-wise installation, HA mode, etcd isolation, and so on. These should be realized step by step using RKE2 and a few options will also be removed (such as helm add-on)

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

1 participant