This message was deleted.
# generala
adamant-kite-43734
01/16/2025, 9:31 PMThis message was deleted.
s
square-tiger-44280
01/16/2025, 9:33 PMHere's how it looks
c
creamy-pencil-82913
01/16/2025, 9:45 PMWhat version of Rancher are you running
s
square-tiger-44280
01/16/2025, 9:48 PMv2.10.1
c
creamy-pencil-82913
01/16/2025, 9:51 PMYou’re on a newer version of Kubernetes than Rancher 2.10 currently supports.
creamy-pencil-82913
01/16/2025, 9:53 PMIf you go to provision a new cluster, note the versions of K3s listed in the dropdown. Those are the patch releases Rancher supports. If you import a cluster that is newer than that, Rancher of course cannot upgrade it to an even newer version until that is added to the rancher metadata.
creamy-pencil-82913
01/16/2025, 9:55 PMyou can also check
Copy code
curl -sL <https://releases.rancher.com/kontainer-driver-metadata/release-v2.10/data.json> | jq -r '.k3s.releases[] | .version's
square-tiger-44280
01/16/2025, 9:57 PMAh, right, makes sense, just reviewed support matrix for 2.10 and it is v1.31. Could have thought of that - thanks. But also, my cluster is on rpi (arm64), if support for newer version is added, will I be able to upgrade?
c
creamy-pencil-82913
01/16/2025, 9:57 PMyou can upgrade when you have something newer to upgrade to
creamy-pencil-82913
01/16/2025, 9:57 PMso, when 1.31.5 or 1.32.x is added to that metadata.
s
square-tiger-44280
01/16/2025, 9:59 PMyup, I understand - thanks much Brad
9 Views