mirror of
https://github.com/kata-containers/kata-containers.git
synced 2026-07-26 07:30:19 +00:00
65e4fa0dc2
Add an opt-in "devkit" path to kata-deploy that wires the devkit debug guest extension into a dedicated per-shim runtime, so operators can debug a sandbox with a rich shell without touching their normal RuntimeClasses. Helm gains a `devkit` value (only effective together with `debug`, since the debug console must be enabled to reach it). When set it emits DEVKIT=true and, for every enabled shim, an extra `kata-<shim>-devkit` RuntimeClass reusing the shim's overhead and node selectors. The RuntimeClass template is refactored to compute name/handler from an optional `variant`, keeping existing behavior. In the deploy binary, DEVKIT synthesizes one kata-<shim>-devkit custom runtime per enabled shim. Modeling it as a custom runtime reuses the whole custom runtime install/register/cleanup machinery; the only devkit-specific piece is a 25-devkit.toml drop-in that cold-plugs the extension image (guest_extension_images name="devkit", with verity_params read from root_hash_devkit-extension.txt when present) and points the agent debug console at /run/kata-extensions/devkit/bin/devkit-sh. The generic rootfs-image-devkit-extension tarball is extracted based on the devkit flag rather than per-shim shim-components.json membership. Signed-off-by: Fabiano Fidêncio <ffidencio@nvidia.com> Assisted-by: Cursor <cursoragent@cursor.com>