https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rke2
a
This message was deleted.
c
Did you go directly from 1.21 to 1.24, or did you step through 1.22 and 1.23?
At this point, all you should need to do is add --disable=rke2-helm-proxy to the servers to make sure they clean it up
b
Straight through.
I might have missed the part about stepping through. Is that the recommended way to upgrade?
I also do not see that option for 
rke2 server --help
.
The only generic disable option: 
--disable value                               (components) Do not deploy packaged components and delete any deployed components (valid items: rke2-coredns, rke2-ingress-nginx, rke2-metrics-server)
I should clarify, we went direct from 1.21 to 1.24. Straight through might imply we went 1.21, 1.22, 1.23 to 1.24.
c
yeah that’s not supported. See https://kubernetes.io/releases/version-skew-policy/#supported-component-upgrade-order
the Kubernetes project recommends that you do the following to benefit from as many regression and bug fixes as possible during your upgrade:
• Ensure that components are on the most recent patch version of your current minor version.
• Upgrade components to the most recent patch version of the target minor version.
For example, if you’re running version 1.26, ensure that you’re on the most recent patch version. Then, upgrade to the most recent patch version of 1.27.
if you’re several minors back, you should do that for each step. 1.21.x -> latest 1.21 -> latest 1.22 -> latest 1.23 -> latest 1.24
the version you’re on doesn’t list rke2-kube-proxy any more because it’s not been packaged with rke2 for several releases, but adding it to that flag should ensure that it’s removed from any servers that still have it due to stepping over releases that would have removed it.
b
Gotcha. Thank you very much for the information.
3 Views
Open in Slack
PreviousNext
Powered by