https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# general
a
This message was deleted.
✅ 1
t
Okay, I found out that I'm using the wrong RKE version. I currently have v1.3.12, but I need v1.3.11. v1.3.11 offers v1.22.9-rancher1-1, which is the only 1.22 version officially supported by Rancher
t
It should be possible to expand the number of Kubernetes upgrade options without upgrading Rancher https://rancher.com/docs/rancher/v2.6/en/admin-settings/k8s-metadata/
t
@tall-school-18125 Thanks for your reply! That's good to know, I was not aware of this. Although I think I will likely take the safer route and use the k8s version that is officially supported as per Rancher docs. Once 2.6.7 is released I will patch k8s accordingly.
@tall-school-18125 Am I going to have any issues when I use rke-1.3.13 to provision v1.22.9-rancher1-1 in my cluster.yml? Only v1.22.11-rancher1-1 is listed when I run 
rke-1.3.13 config --list-version --all
. But it successfully goes through when I run 
rke up
in my test environment and I'm not seeing any problems yet. Are older k8s patches automatically supported as well by rke releases that list newer patches for that specific minor version?
t
I wouldn't expect issues, but we only support the latest patch version for each minor version because that is what was used for testing and that would also contain important security fixes
t
Alright, I see. I really appreciate you taking the time to reply. Thanks and have a nice day!
16 Views
Open in Slack
PreviousNext
Powered by