Fabiano Fidêncio 28414a614e kata-deploy: detect k3s/rke2 via systemd services instead of version string ...

Newer k3s releases (v1.34+) no longer include "k3s" in the containerd
version string at all (e.g. "containerd://2.2.2-bd1.34" instead of
"containerd://2.1.5-k3s1"). This caused kata-deploy to fall through to
the default "containerd" runtime, configuring and restarting the system
containerd service instead of k3s's embedded containerd — leaving the
kata runtime invisible to k3s.

Fix by detecting k3s/rke2 via their systemd service names (k3s,
k3s-agent, rke2-server, rke2-agent) rather than parsing the containerd
version string. This is more robust and works regardless of how k3s
formats its containerd version.

Signed-off-by: Fabiano Fidêncio <ffidencio@nvidia.com>

2026-04-01 14:24:55 +02:00

..

osbuilder

gpu: Update chiseled rootfs with new CDH deps

2026-03-16 09:43:17 -07:00

packaging

kata-deploy: detect k3s/rke2 via systemd services instead of version string

2026-04-01 14:24:55 +02:00

testing

gatekeeper: unrequire kata-deploy k3s tests

2026-03-31 18:32:17 +02:00

containerd-shim-katadbg-v2

tests: Make editorconfig-checker happy

2026-02-10 21:58:28 +01:00