Max Gautier
Max Gautier
Ok, I see the rationale. I'm still not a very big fan, especially because this opens the door for subtle bugs where the containerd config is not updated with new...
Also, following my previous message, could `containerd_additional_runtimes` currently be used for solving this ? https://github.com/kubernetes-sigs/kubespray/blob/b04ceba89b9094275cd913e24ec7f43eb0f17cf0/roles/container-engine/containerd/templates/config.toml.j2#L43
I haven't forgot this, I'm just a bit swamped at work right now ; I'll come back to this soonish.
We should probably come up with consistent guidance on what /kind to use for versions upgrades, because we're all over the place ^. Besides, look ok to me, and I...
Is there a link/docs to that ? I'm all for aligning ourselves with the broader k8s community, especially on tooling.
@yankay We can release as-is, I think.
This is apparently not enough because the CI runners can't extract the cache because they don't have gitlab-runner : https://gitlab.com/kargo-ci/kubernetes-sigs-kubespray/-/jobs/7698277164#L124
@ant31 if you have an idea
https://gitlab.com/kargo-ci/kubernetes-sigs-kubespray/-/jobs/7698277164#L524 I think it's app.vagrantup.com for the vagrant boxes used by molecule.
/hold This needs change in the CI cluster (configure either an S3 or volume cache for the gitlab-runner) before it can work.