This message was deleted.
# general
a
This message was deleted.
b
So when is Rancher 2.7.9 available in the Rancher applications list? Currently it isn't. Even though it is available in the stable helm repository...
b
Rancher applications list? Not sure what that is... Rancher is installed via helm.
b
Rancher UI -> Cluster manager -> local -> Apps. The Rancher version is 2.7.6 there. Normally stable and supported upgrades appear there.
This is probably my bad... you need to add the Rancher repo to be able to do that. I didn't in my test cluster.
s
I think it's generally recommended to update Rancher via helm outside of the Rancher UI
b
Hm... back in the days I was told about in a Rancher training. And in general it's not different to the outside helm update. It's just using helm in a container...
s
The container though is controlled by rancher, which is being upgraded
b
To be 100% correct it's only created by Rancher. It's controlled by RKE2 (in my case). But I don't want to argue. It's working both ways... and if it should not work, Rancher had done something against it 🙂
s
The container will be created and junked given rancher needs. The UI also proxies requests via the rancher backed, which will be changed as part of the upgrade. Generally it isn't a path that's tested, documented or generally supported. We would recommend the steps as per https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrades
b
I guess my Suse trainer did not show this method to me alone. If you really think this is wrong, you should update your docs accordingly.
s
i'm happy to have a chat with the trainer to update either my or their advice. Could you advise where you received the information or link to the docs?
b
It was an in-person training. >1 year ago.