I had a quick question regarding the versions recommended on the k3s airgap image list. I see these versions don't align with the upstream k8s ones mentioned with kubeadm constants. For eg. v1.26.1 k3s, pause version mentioned in k3s airgap list is 3.6 and the one on upstream k8s is 3.9. Similar for coredns k3s 1.9.4 and k8s upstream is 1.9.3. Q1) Is there any specific reason behind this? May be related to performance/issues observed with k3s binary. Q2) Should we align to k3s airgap versions or to the upstream k8s versions? If anyone of k3s folks can comment on this. Would be great. Thanks!

A1) Sometimes we do see issues with different packaged versions, so we’ll either mirror and fix or just use a different version that doesn’t have that issue. For these specific ones, I’m not sure of any issues off the top of my head. It could be that we noticed coredns had a bump before upstream, and that we didn’t catch the pause bump. Shouldn’t have too much of an effect either way. A2) You should align to the k3s airgap versions since that is what k3s is using and expecting