https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rke2
a
This message was deleted.
c
That was resolved with newer releases, are you on a fixed release?
w
2.7.4 is latest non debug/rc release
c
You should be looking at the rke2 version, not rancher.
w
Sorry, I'm not following.. Installed rancher and rke comes with it. How do I bump rke2 independent of rancher?
c
That's not quite right. Rancher can provision rke, rke2, or k3s. It's not quite right to say that it comes with rke. How are you running rancher? Are you using it to provision rke2 clusters?
Or did you install rke2, and then deploy rancher on top of that?
w
I used a helm chart
Rancher installed to k3s
c
if you’re asking about provisioning rke2 clusters, yes that is driven by that data.
w
Are you talking about this? specifically 
rke2-upgrade
? https://docs.rke2.io/upgrade/automated_upgrade
c
That is managed by the Rancher team; they periodically release new RKE2 versions for provisioning by Rancher
w
I've never thought of upgrading rke2 independent of rancher. It sounds like that's what you're proposing?
c
If you are using Rancher to provision your clusters, you should use Rancher to upgrade it. If you have provisioned your RKE2 clusters manually, then you could use the steps documented on that page to upgrade it.
w
ahh yeah, ok . I'm using rancher to do it.
thank you for clarifying. So i guess my only recourse is node ports / downgrade k8s
or i guess klipper?
14 Views
Open in Slack
PreviousNext
Powered by