This message was deleted.
# general
a
This message was deleted.
c
Rancher 2.6 doesn’t support Kubernetes 1.25. You should have upgraded to 2.7.2 (the first release to support 1.25) prior to upgrading your cluster.
1
m
hmm
Copy code
If your charts get stuck in this state, please consult the Rancher docs on how to clean up your Helm release secrets.
found this in the github link
guess I didn't think the order really mattered but makes sense I suppose
c
absolutely does
1
m
Well yes that is obvious in retrospect. If I cleanup all resources in cattle-system will that purge the ui?
c
I am honestly not sure what the best path forward is. If you have a backup you might restore back to before you upgraded. If not you might have to push forward and upgrade to 2.7.2.
Deleting stuff at random is probably not a good idea.
m
I only use rancher as a ui, I do have a backup and can likely rollback rke as well but just painful
Does a rollback restart other helm deployed resources?
(rancher-ui restore)
yeah it's very dead, oh well i'll have to kill it and start again
Does rancher-stable not support 1.25.6? can't even fresh install rancher
c
rancher-stable from where? In general stable isn’t updated to point at a new release until after it’s been out for a bit, and 2.7.2 just came out a day or two ago.
m
I figured out what happened I was using the wrong helm variable to disable psp. I had to manually purge rancher from my cluster by deleting cattle-system, the mutating webhook thing and then reinstalling it. Sadly due to a auto https forwarding configuration error cert-manager is unable to finish the acme signing process so just waiting for devops to fix it so I can finish setting rancher back up and then restore the backup
Lucky that all my applications are deployed via helm & a ci pipeline and rancher is JUST a ui
I believe everything would of been fine with the upgrade had I realized the incorrect helm variable
but it is what it is
d
What was the right helm variable and value?
1059 Views