mirror of
https://github.com/kata-containers/kata-containers.git
synced 2026-07-26 15:55:24 +00:00
c3a7e3dee9
microk8s 1.35 ships an on-disk `version = 2` containerd-template.toml using the legacy `io.containerd.grpc.v1.cri` plugin, even though it bundles containerd 2.1.3. Making the guest-pull / nydus tests pass there required kata-deploy to write the post-migration split-CRI images-service snapshotter mapping (`io.containerd.cri.v1.images.runtime_platforms`), which in turn meant picking the CRI plugin id from the containerd binary version rather than the template's declared schema. That workaround only existed to satisfy microk8s and polluted the shared kata-deploy config logic. Rather than carry that workaround, stop running the guest-pull coco tests (nydus and experimental-force-guest-pull, qemu-coco-dev and qemu-coco-dev-runtime-rs) on microk8s. k0s, k3s and rke2 keep full guest-pull coverage; they already worked without the kata-deploy change. microk8s still runs the kata-deploy functional tests, so the host memory footprint reduction and the OCI policy drop-in for microk8s are kept. Signed-off-by: Fabiano Fidêncio <ffidencio@nvidia.com> Assisted-by: Cursor <cursoragent@cursor.com>