This message was deleted.

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