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
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)
The text was updated successfully, but these errors were encountered:
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)
The text was updated successfully, but these errors were encountered: