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
Hello @brandond, we are considering moving to RKE2 for kube-hetzner, we are currently using k3s.
In terms of performance, ressource need, will we loose anything? It seems to me not that much, correct? At first, we were considering supporting both, but now that I see you ship RPMs for it, it changes everything.
Do you have a repo for it, so that MicroOS can update RKE2 along with the rest of the packages via transactional-update? If so what is the repo for it, is it the standard rancher repo?
So that would remove the need for the system upgrade controller, correct? Used along with kured the upgrade should be seamless I imagine.
Any light you can give me would be super helpful, thank you!
The text was updated successfully, but these errors were encountered:
Hello @brandond, we are considering moving to RKE2 for kube-hetzner, we are currently using k3s.
In terms of performance, ressource need, will we loose anything? It seems to me not that much, correct? At first, we were considering supporting both, but now that I see you ship RPMs for it, it changes everything.
Do you have a repo for it, so that MicroOS can update RKE2 along with the rest of the packages via transactional-update? If so what is the repo for it, is it the standard rancher repo?
So that would remove the need for the system upgrade controller, correct? Used along with kured the upgrade should be seamless I imagine.
Any light you can give me would be super helpful, thank you!
The text was updated successfully, but these errors were encountered: