This message was deleted.
# k3s
a
This message was deleted.
h
What version is your rancher? There are supported version of kubernetes for Rancher - see this support matrix: https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-8-4/
h
Thanks for the reply. I am running Rancher v2.8.3 and my imported cluster was already on v1.28.8+k3s1. So why can't I see version between v1.28.8+k3s1 and v1.28.10+k3s1 there in the list? From where does it pick these versions up? And, how can I customize this list?
n
1. You can't customize the list, its based on the Rancher and what versions of K3s it supports 2. Versions get picked up in https://github.com/rancher/kontainer-driver-metadata Looks like it might be a Rancher specific issue
h
Can we update kubernetes version for an imported cluster ? I do not have any imported clusters into rancher UI (except for the local) so this is new for me. And, for rancher-local the kubernetes updates are not from rancher UI (atleast not yet in 2.7.10)
h
Hi @nutritious-tomato-14686, thanks for your response. if it's an airgapped environment, it won't be able to reach https://github.com/rancher/kontainer-driver-metadata For my usecase, I will not use the UI anyway. I need to programmatically instruct Rancher to provision K3s upgrades. Could you point me to a doc or any resource that could help me achieve the automation of k3s upgrade using a private repo. I need to rollout k3s upgrade for my local and imported k3s clusters. Thanks in advance