https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rke2
a
This message was deleted.
c
The SUC deployment managed by Rancher is used to upgrade the rancher-system-agent binary and systemd service that is installed on the nodes. It does not use the charts or manifests from the SUC repo.
They are in the process of getting moved from rancher/rancher to rancher/system-upgrade-controller, but the ones currently used by rancher are here: https://github.com/rancher/charts/tree/dev-v2.11/charts/system-upgrade-controller
w
ok, is it recommended to apply custom plans to the cattle-system namespaces then? My goal is to update rke2.
c
I think it is set up to watch plans in all namespaces? I wouldn’t put custom plans in cattle-system, no.
But don’t do that. If you’re using Rancher to provision the cluster you must use Rancher to set the RKE2 version. Don’t use the SUC to upgrade the cluster out from under Rancher, it will get VERY mad at you for that.
w
OK, I'll check if I get rke2 upgraded by using rancher. I had an issue with that feature in 2.10.7. Just testing with 2.11.1...
c
You had an issue with upgrading Rancher-provisioned clusters using Rancher?
w
It was an imported generic rke2 cluster created with rancher.
c
wait did you import it into rancher, or create it with rancher? the difference is important.
w
It was created with an rancher version 2.6.x. I reinstalled rancher and then imported the rke2 cluster.
Reinstallation was due to ciircumstances....
c
ah. In that case yeah its going to be in a bit of an odd state
w
As you mention this. Another odd behavior is that the cluster irregular disconnects from rancher every 2-3 days. This happens sonce it is imported.
12 Views
Open in Slack
PreviousNext
Powered by