PAGES
← all tools
◆ Container & Image Security

kata-containers

4.3.0 open-source

Kata Containers builds lightweight Virtual Machines that feel and perform like containers but provide the workload isolation and security advantages of VMs.

Summary

Kata-containers is an open-source container runtime, licensed under Apache 2.0, that runs each container inside a lightweight virtual machine so workloads get VM-level isolation while still behaving like a standard container. It's installed on host systems as a runtime component, using kata-deploy or Helm to configure it, and is aimed at platform and infrastructure teams running Kubernetes who need stronger tenant isolation than namespace-based containers provide. Its own documentation frames it as an alternative to standard container runtimes like runC, replacing shared-kernel isolation with per-container VMs while keeping container-like startup and performance. It supports x86_64, ARMARMA family of RISC processor architectures designed by Arm Holdings and licensed to chip makers worldwide; tools target it to run natively on mobile, embedded, and increasingly server and desktop hardware., IBM Power and IBM Z hardware, and recent work includes a Rust rewrite of the runtime, a built-in Dragonball VMMVMMA Virtual Machine Monitor is software that creates and manages virtual machines, abstracting physical hardware so multiple OS instances run in isolation; cyber tools use it to sandbox execution or emulate target environments safely., dm-verity-backed root filesystems, and GPUGPUA graphics processing unit, a processor that performs many calculations in parallel. AI workloads use GPUs to speed up model training and inference. passthrough across QEMUQEMUAn open-source machine emulator and virtualizer that lets software run a guest OS or CPU architecture on a different host, giving cyber tools an isolated, inspectable execution environment without dedicated hardware., Cloud Hypervisor and Dragonball.

Kata Containers builds lightweight Virtual Machines that feel and perform like containers but provide the workload isolation and security advantages of VMs.

How kata-containers helps

Which of my Kubernetes workloads could break out of their container and touch the host kernel?

each pod runs inside its own lightweight VM with a separate kernel, so a compromised container faces hypervisor-level isolation instead of a shared kernel it might escape

Can a noisy or malicious tenant on this cluster see or affect another tenant's containers?

per-container VM boundaries mean tenants no longer share a kernel, so kernel-level attacks and side-channels that work against namespace isolation stop at the VM edge

Has my container image been tampered with before it reaches production?

the root filesystem can be backed by dm-verity integrity verification, enabled by default in deployment configs, so any modification to the image is detected before it runs

Are my GPU workloads still isolated the same way as everything else on this cluster?

GPU device passthrough is supported across QEMU, Cloud Hypervisor and Dragonball, so accelerated workloads run inside the same per-container VM boundary rather than dropping back to shared-kernel access

Is my sensitive workload's memory or scratch storage exposed through shared filesystem paths?

block-based emptyDir volumes avoid filesystem sharing between host and guest, and unsafe emptyDir behavior that let volumes exceed their configured size limit has been removed

Will switching to VM-level isolation cost me container-like startup speed and scheduling accuracy?

improved static sandbox resource sizing accounts for runtime overhead so Kubernetes Pod Overhead and scheduling reflect the real cost, while the built-in Dragonball VMM gives lightweight VM startup without requiring QEMU or Cloud Hypervisor

all 61 features, with the evidence for each →

Languages

Not documented

Features

61 capabilities across 7 areas · 4 backed by code, an API document or a real run

Built from kata-containers's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What kata-containers offers you

  • Command-line interface5
  • Kubernetes-native deployment2
Hypervisor and VMM Support 2 capabilities Kata Containers runs workloads inside lightweight virtual machines, and this area covers the hypervisors and virtual machine monitors available to back those VMs. Users can choose between QEMU, Cloud Hypervisor, and the built-in Dragonball VMM depending on their environment and requirements.
Rust runtime (runtime-rs) verified Provides a Rust-based runtime as the default engine for running Kata Containers VMs across x86_64, ARM, and IBM s390x systems. 23 releases · 1 other source · first seen Apr 2024

release 23 total

  • Enables rootless SEV-SNP and TDX in runtime-rs/QEMU, allowing confidential VMs to run without root privileges.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ 4.3.0 · Oct 2026 · source · release history
  • Enable QEMU sandbox for NVIDIA configs in runtime-rs 4.2.0 · Sep 2026 · source · release history
  • Cold-plug block devices requested before boot in runtime-rs 4.2.0 · Sep 2026 · source · release history
  • Pass block sources by file descriptor in runtime-rs/QEMU 4.2.0 · Sep 2026 · source · release history
  • runtime-rs adds support for Cloud Hypervisor VM templates for preconfigured VM states 4.1.0 · Aug 2026 · source · release history
  • Disables QEMU features and devices by default to reduce the attack surface. 4.1.0 · Aug 2026 · source · release history

command line

  • --tls-min-version — Minimum TLS version (VersionTLS12, VersionTLS13). Defaults to VersionTLS12 when TLS is enabled. 4.2.0 · Sep 2026 · command-line history
Dragonball built-in VMM shipped Offers Dragonball as a built-in VMM so users can run containers without installing QEMU or Cloud Hypervisor. 11 releases · 1 other source · first seen May 2021

release 11 total

  • Adds support for Dragonball as a built-in VMM alternative to QEMU and Cloud Hypervisor 4.0.0 · Jul 2026 · source · release history
  • Adds Dragonball as a built-in VMM default, supporting virtio-net, virtio-blk, and VFIO device passthrough without requiring QEMU or Cloud Hypervisor. 4.0.0 · Jul 2026 · source · release history
  • dragonball gains a userspace IOAPIC implementation to enable the split irqchip architecture. 3.30.0 · May 2026 · source · release history
  • Enables Dragonball sandbox runtime exclusively on x86_64 and aarch64 architectures 3.15.0 · Mar 2025 · source · release history
  • Dragonball sandbox runtime is now restricted to x86_64 and aarch64 architectures only; other platforms will not build or run with it 3.15.0 · Mar 2025 · source · release history
  • Adds QMP support for QEMU in runtime-rs (runtime-rs: add QMP support for Qemu(part I)) 3.6.0 · Jun 2024 · source · release history

docs

  • Open source lightweight VM-based container runtime providing workload isolation with VM-level security and container-like performance.
Device Passthrough and Hardware Access 5 capabilities Kata Containers can expose physical and virtual hardware devices directly to containers running inside VMs, enabling workloads that require low-latency or specialised hardware. This area covers the mechanisms for attaching GPUs, VFIO devices, network interfaces, and IBM Z cryptographic accelerators to sandboxed workloads.
GPU device passthrough shipped Enables GPU devices to be passed through into containers across all three supported hypervisors. 12 releases · 1 other source · first seen Oct 2022

release 12 total

  • Accepts a complete driver source tarball as driver.url for NVIDIA GPU builds. 4.3.0 · Oct 2026 · source · release history
  • Adds support for a dedicated driver userspace repository for NVIDIA GPUs via driver.url in nvgpu. 4.3.0 · Oct 2026 · source · release history
  • Expands guest-extensions support to VMMs beyond QEMU, updates Cloud Hypervisor to v53.0, and bumps the guest kernel to 6.18.52. 4.3.0 · Oct 2026 · source · release history
  • Adds virtio-rng entropy device to the dragonball VMM. 4.2.0 · Sep 2026 · source · release history
  • Adds nvswitch-class device passthrough support in the runtime, enabling NVSwitch-based GPU topologies. 4.1.0 · Aug 2026 · source · release history
  • Adds GPU device support across QEMU, Cloud Hypervisor, and Dragonball hypervisors. 4.0.0 · Jul 2026 · source · release history

example

  • Point nvgpu at a dedicated driver userspace repository or a full driver source tarball so every GPU runtime class component is built and shipped. # In the nvgpu driver configuration, set driver.url to a dedicated repository or a complete tarball: driver: url: "https://internal-mirror.example.com/nvidia-driver-570.tar.gz" 4.3.0 · Oct 2026 · source
VFIO device passthrough shipped Lets users pass physical devices directly into a container VM using the VFIO framework, including CDI-based attachment for single-container workloads. 12 releases · first seen Nov 2021

release 12 total

  • Pass VFIO devices by file descriptor in runtime-rs/QEMU 4.2.0 · Sep 2026 · source · release history
  • Passes VFIO devices by file descriptor in runtime-rs/QEMU, enabling fd-based VFIO device handoff. 4.2.0 · Sep 2026 · source · release history
  • Unused VFIO configuration options were removed. 4.0.0 · Jul 2026 · source · release history
  • Adds VFIO device cold-plug support, including CDI-based VFIO cold-plug in single-container (non-pod-sandbox) mode. 4.0.0 · Jul 2026 · source · release history
  • clh: Add VFIO device cold-plug support to the Cloud Hypervisor runtime 3.29.0 · Apr 2026 · source · release history
  • cri-o.device-coldplug annotation support in shim for device hot-add without restart 3.27.0 · Feb 2026 · source · release history
SR-IOV and network interface hot-plug shipped Allows network interfaces to be added to a running VM and improves SR-IOV support for high-throughput networking with multi-queue propagation. 3 releases · first seen Oct 2024

release

  • Adds improved network interface hot-plug for QEMU with enhanced SR-IOV support. 4.0.0 · Jul 2026 · source · release history
  • Propagates multi-queue networking configuration through all supported hypervisors (QEMU, Cloud Hypervisor, Dragonball). 4.0.0 · Jul 2026 · source · release history
  • Adds network device hotplugging capability to qemu-rs 3.10.0 · Oct 2024 · source · release history
IBM s390x VFIO-AP mediated device support shipped Exposes IBM Z hardware cryptographic and accelerator devices to containers on s390x systems via VFIO-AP mediated device passthrough. 2 releases · first seen Feb 2025

release

  • Adds s390x VFIO-AP mediated device support for IBM Z crypto and accelerator workloads. 4.0.0 · Jul 2026 · source · release history
  • Enables VFIO-AP coldplug support for s390x architectures 3.14.0 · Feb 2025 · source · release history
Host network namespace device placement shipped Allows network devices to be placed in the host network namespace rather than inside the VM when using QEMU. 1 release · first seen Jul 2026

release

  • Adds support for placing network devices in the host network namespace when using QEMU. 4.0.0 · Jul 2026 · source · release history
Storage and Block Device Management 6 capabilities This area covers how Kata Containers attaches, manages, and exposes storage to workloads running inside VMs. It includes root filesystem drivers, volume types, thin-provisioned storage, and the unified model for managing block devices across hypervisors.
Unified block device model (BlockModern) shipped Provides a single consistent model for attaching and detaching block devices across all supported hypervisors, with automatic rollback if an operation fails. 9 releases · 1 other source · first seen Oct 2020

release 9 total

  • Remove unsupported disable_block_device_use configuration option from runtime-rs 4.2.0 · Sep 2026 · source · release history
  • Enables cold-plug of block devices requested before boot in runtime-rs with Cloud Hypervisor. 4.2.0 · Sep 2026 · source · release history
  • Passes block storage sources by file descriptor in runtime-rs/QEMU, enabling more secure and flexible block device attachment. 4.2.0 · Sep 2026 · source · release history
  • Shares block storage source mapping in runtime-rs to reduce duplication. 4.1.0 · Aug 2026 · source · release history
  • Adds a unified block device model (BlockModern) across QEMU, Cloud Hypervisor, and Dragonball, with improved hot-plug/unplug reliability and rollback on failure. 4.0.0 · Jul 2026 · source · release history
  • Introduces an iothreads framework for virtio-blk devices, allowing independent I/O processing threads for storage performance. 3.24.0 · Dec 2025 · source · release history

example

  • Validate the guest agent's state and capabilities using the new CLI tool. agent-ctl GetGuestDetails 2.0.0 · Oct 2020 · source
Block-based emptyDir volumes shipped Backs Kubernetes emptyDir volumes with a dedicated block device instead of a shared filesystem, improving both performance and isolation. 4 releases · first seen Aug 2024

release

  • Adds block-based emptyDir volumes (block-plain) for improved performance and security, avoiding filesystem sharing. 4.0.0 · Jul 2026 · source · release history
  • Unsafe emptyDir setting that allowed volumes to exceed their sizeLimit has been removed. 4.0.0 · Jul 2026 · source · release history
  • Trusted image storage capability is introduced. 3.8.0 · Aug 2024 · source · release history
  • genpolicy validates each exec command line argument (container.exec_commands). 3.8.0 · Aug 2024 · source · release history
SPDK storage backend integration verified Connects Kata Containers to an SPDK storage backend by letting users configure vhost controller sockets, backing disk paths, and RPC timeouts. 1 release · 3 other sources · first seen May 2021

release

command line

  • --spdk-vhostpath — path for spdk vhost controller sockets 3.22.0 · Oct 2025 · command-line history
  • --spdk-rpc-timeout — timeout for SPDK JSON-RPC requests 3.22.0 · Oct 2025 · command-line history
  • --spdk-rawpath — path for spdk rawdisk backing files 3.22.0 · Oct 2025 · command-line history
EROFS snapshotter support shipped Adds support for the EROFS read-only snapshotter so container images can be served from an EROFS-formatted snapshot with prerequisite checks before deployment. 3 releases · first seen May 2025

release

  • Adds support for EROFS snapshotter, available through Helm configuration, with kata-deploy validating EROFS prerequisites before installation. 4.0.0 · Jul 2026 · source · release history
  • kata-deploy: Add the ability to set up different snapshotters (nydus & erofs) allows configuring the container runtime snapper in the deployment manifest. 3.22.0 · Oct 2025 · source · release history
  • Adds EROFS Snapshotter Support to Kata containers for faster image processing. 3.17.0 · May 2025 · source · release history
Thin-provisioned storage discard and unmap shipped Enables thin-provisioned storage to reclaim space by issuing discard and unmap commands when supported by the underlying hypervisor. 1 release · first seen Jul 2026

release

  • Adds discard and unmap support for thin-provisioned storage (requires hypervisor support). 4.0.0 · Jul 2026 · source · release history
virtio-scsi container root filesystem driver shipped Allows containers to use a virtio-scsi device as their root filesystem, giving an alternative to the default block driver. 1 release · first seen Jul 2026

release

  • Adds improved virtio-scsi support as a container root filesystem driver. 4.0.0 · Jul 2026 · source · release history
Security and Integrity 2 capabilities Kata Containers uses VM-level isolation as its primary security boundary, and this area covers the additional integrity and verification mechanisms layered on top. It includes verified boot for the guest root filesystem and memory hotplug support that stays within the trusted VM boundary.
dm-verity integrity-verified root filesystem shipped Verifies the integrity of the guest root filesystem using dm-verity so tampering with the image is detected before it is used. 5 releases · first seen Sep 2024

release

  • The image_guest_pull driver option metadata is removed from genpolicy, agent, and runtime(-rs) — configurations or policies that set this field will break. 4.3.0 · Oct 2026 · source · release history
  • Verifies guest-pulled image references in genpolicy. 4.3.0 · Oct 2026 · source · release history
  • Adds dm-verity integrity-verified root filesystem support, enabled by default in deployment configurations. 4.0.0 · Jul 2026 · source · release history
  • Adds GPT/VMDK support for integrity-verified root filesystems. 4.0.0 · Jul 2026 · source · release history
  • image-rs (agent) now checks extended attributes (xattrs) during image unpacking for stricter security 3.9.0 · Sep 2024 · source · release history
virtio-mem memory hotplug shipped Allows memory to be added to a running VM guest using the virtio-mem protocol, keeping memory expansion within the secure VM environment. 5 releases · first seen May 2021

release

  • Adds virtio-mem memory hotplug support in runtime-rs. 4.0.0 · Jul 2026 · source · release history
  • Adds memory prealloc support for qemu/ch hypervisors in runtime-rs 3.18.0 · Jun 2025 · source · release history
  • Adds reclaim_guest_freed_memory configuration option for both qemu and cloud-hypervisor hypervisors to allow host reclamation of freed guest memory 3.14.0 · Feb 2025 · source · release history
  • Adds support for swap devices within the guest OS 2.3.0 · Nov 2021 · source · release history
  • Adds virtio-mem support for dynamic memory management in the guest kernel (requires CONFIG_VIRTIO_MEM enabled) 2.1.0 · May 2021 · source · release history
Resource Management and Scheduling 1 capability This area covers how Kata Containers accounts for and controls the compute resources consumed by sandboxed workloads. Accurate resource sizing helps Kubernetes schedule pods correctly and prevents the VM overhead from being invisible to the scheduler.
Static sandbox resource sizing shipped Calculates sandbox resource requests to include the overhead of the VM runtime itself, so Kubernetes Pod Overhead and scheduling decisions reflect actual consumption. 7 releases · first seen Oct 2020

release 7 total

  • Improves static sandbox resource sizing to account for runtime overhead values, benefiting Kubernetes Pod Overhead and scheduling accuracy. 4.0.0 · Jul 2026 · source · release history
  • static resource management functionality available via config keys in runtime-rs. 3.0.0 · Oct 2022 · source · release history
  • Adds CONFIG_CGROUP_HUGETLB kernel option to the base image to enable hugetlb cgroups 2.5.1 · Sep 2022 · source · release history
  • Add static_sandbox_resource_mgmt flag to enable static CPU management for better initial VM sizing when sandbox resource requirements are specified (requires containerd >= 1.6, Kubernetes >= 1.23) 2.4.0 · Apr 2022 · source · release history
  • Introduces static sandbox resource management in the runtime to control resource allocation. 2.4.0-alpha2 · Feb 2022 · source · release history
  • kata-deploy now automatically includes pod overhead in the generated runtime class configurations. 2.0.3 · Apr 2021 · source · release history
Deployment and Configuration 1 capability This area covers the mechanisms for deploying, configuring, and scoping Kata Containers in a cluster. It includes namespace-level filtering to control where the runtime applies and version-pinning support for reproducible Helm-based installations.
Namespace filtering verified Lets administrators restrict which namespaces use Kata Containers by applying a regular expression filter, and supports pinning the Helm chart version at deploy time. 1 release · 2 other sources · first seen Mar 2023

Also counts toward: Command-line interface

release

  • virtcontainers: introduce hypervisor_darwin with Darwin skeletons for Linux subsystems to enable macOS development. 3.1.0 · Mar 2023 · source · release history

command line

  • --only-namespaces-regexp — Regexp namespace filter applied after --exclude-namespaces 3.23.0 · Nov 2025 · command-line history
  • --set — "${CHART}" --version "${VERSION}" 3.23.0 · Nov 2025 · command-line history
Other 44 capabilities
Observability via kata-monitor shipped Improves observability and manageability of the runtime through the dedicated kata-monitor component. 14 releases · first seen Oct 2020

Also counts toward: Command-line interface

release 14 total

  • Add kata-monitor TLS support for secure monitoring communication 4.2.0 · Sep 2026 · source · release history
  • Adds TLS support to kata-monitor for encrypted metrics exposure.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ 4.2.0 · Sep 2026 · source · release history
  • Captures early guest console logs in the runtime before the agent is fully up. 4.2.0 · Sep 2026 · source · release history
  • Add support for monitoring disk usage via statfs to Metrics 3.32.0 · Jun 2026 · source · release history
  • Adds the sandbox API implementation allowing external management of Kata sandboxes 3.14.0 · Feb 2025 · source · release history
  • kata-agent supports cgroups-v2 via systemd.unified_cgroup_hierarchy configuration, allowing modern container cgroup management inside the guest VM. 3.4.0 · Apr 2024 · source · release history
Rust-based kata-agent shipped Utilizes a Rust rewrite of the agent to reduce memory overhead and overall attack surface. 11 releases · 1 other source · first seen Oct 2020

release 11 total

  • kata-deploy: Allow users to set experimental_force_guest_pull adds a helm chart option to force guest-side image pulling. 3.22.0 · Oct 2025 · source · release history
  • runtime-rs: add seccomp support for dragonball enables Seccomp filtering within the Dragonball VMM. 3.22.0 · Oct 2025 · source · release history
  • runtime-rs adds seccomp syscall filtering for the Cloud Hypervisor runtime 3.20.0 · Aug 2025 · source · release history
  • Adds runtime: add option to force guest pull to allow pulling images inside the guest environment 3.18.0 · Jun 2025 · source · release history
  • Supports pulling images in guest using Kata Volumes for CoCo in runtime-rs 3.18.0 · Jun 2025 · source · release history
  • FSGroup support added for the guest agent. 3.0.0 · Oct 2022 · source · release history

example

  • Build a statically linked kata-agent without Seccomp to avoid static build failures. cd ./src/agent && make SECCOMP=no 2.3.0 · Nov 2021 · source
TDX hardware support shipped Enables Intel Trust Domain Extensions (TDX) for confidential computing workloads via supported hypervisors. 10 releases · first seen Apr 2022

release 10 total

  • Adds VIRTIO_F_ACCESS_PLATFORM flag for TDX virtio devices in dragonball, improving TDX guest compatibility. 4.1.0 · Aug 2026 · source · release history
  • Add basic ACPI implementation for TDX boot in dragonball 3.32.0 · Jun 2026 · source · release history
  • runtime-rs: Enhance TDX in qemu with new capabilities 3.29.0 · Apr 2026 · source · release history
  • kata-deploy now includes runtime-rs TDX / SNP runtimeclasses for deploying Intel Trust Domain Extensions and AMD Secure Nested Paging workloads. 3.26.0 · Jan 2026 · source · release history
  • Kata-deploy now automatically deploys NodeFeatureRules for Trusted Execution Environments (TEEs) 3.23.0 · Nov 2025 · source · release history
  • runtime: config: allow TDX QGS port=0 allows setting qemu.qgs_port to 0 in the configuration. 3.22.0 · Oct 2025 · source · release history
Helm chart-based deployment shipped Provides a Helm chart for deploying the cyber toolchain, replacing or supplementing previous deployment methods. 9 releases · first seen Aug 2024

Also counts toward: Kubernetes-native deployment

release 9 total

  • Adds podLabels support on per-node Jobs in kata-deploy. 4.1.0 · Aug 2026 · source · release history
  • Adds values overlay support when publishing the Helm chart in kata-deploy. 4.1.0 · Aug 2026 · source · release history
  • Enables job-mode dispatcher confinement to trusted nodes in kata-deploy. 4.1.0 · Aug 2026 · source · release history
  • Adds TEE key advertisement rendering from the Helm chart in kata-deploy. 4.1.0 · Aug 2026 · source · release history
  • Makes kata-deploy roll out when mounted ConfigMaps change via Helm. 4.1.0 · Aug 2026 · source · release history
  • kata-deploy helm chart supports values overlay when publishing charts for custom deployment configurations 4.1.0 · Aug 2026 · source · release history
virtio-fs shared file system shipped Provides a shared file system using virtio-fs as the default implementation for better POSIX compliance compared to previous alternatives. 7 releases · 1 other source · first seen Oct 2020

release 7 total

  • Implements SharedFS initialization for remote hypervisor configurations to allow shared volume mounts 3.7.0 · Jul 2024 · source · release history
  • Allows specifying virtio_fs_extra_args annotation on containers to pass extra arguments to virtiofsd. 3.2.0 · Oct 2023 · source · release history
  • virtcontainers: introduce hypervisor_darwin with Darwin skeletons for Linux subsystems to enable macOS development. 3.1.0 · Mar 2023 · source · release history
  • inline-virtio-fs added as a shared_fs type in configuration. 3.0.0 · Oct 2022 · source · release history
  • Add new default configuration parameter announce_submounts to virtio-fs settings in the configuration file to prevent inode number collisions 2.4.0 · Apr 2022 · source · release history
  • The default shared file system has changed to virtio-fs; environments relying on virtio-9p behavior must explicitly configure an alternative or accept POSIX compliance differences 2.0.0 · Oct 2020 · source · release history

example

  • Boot a pod VM directly using agent-ctl for debugging or validation without needing the full CRI stack. agent-ctl --vm 3.20.0 · Aug 2025 · source
Drop-in configuration files shipped Supports modular configuration via drop-in files using TOML tree merging capabilities. 6 releases · first seen Oct 2022

release

  • Bumps rootfs base to Ubuntu 26.04 across all images. 4.2.0 · Sep 2026 · source · release history
  • The env.shims, env.defaultShim, env.allowedHypervisorAnnotations, env.snapshotterHandlerMapping, env.pullTypeMapping, env.agentHttpsProxy, env.agentNoProxy, env._experimentalSetupSnapshotter, env._experimentalForceGuestPull (and their per-arch variants like *_x86_64), and env.debug fields are… 3.23.0 · Nov 2025 · source · release history
  • Introduces a new structured configuration format for shims in the kata-deploy helm chart to replace the legacy env.* fields 3.23.0 · Nov 2025 · source · release history
  • kata-deploy supports containerd configuration version 3 via drop-in files 3.12.0 · Dec 2024 · source · release history
  • tools.kata-webhook now allows specifying the runtime class via a configMap 3.10.0 · Oct 2024 · source · release history
  • drop-in config files are now supported via the tomy::Value tree merging in runtime-rs. 3.0.0 · Oct 2022 · source · release history
Direct-assigned volume support shipped Enables direct delegation of block storage volume management from CSI to the runtime agent. 6 releases · first seen Apr 2022

release

  • Isolates guest debug in runtime classes within kata-deploy. 4.1.0 · Aug 2026 · source · release history
  • kata-ctl direct-volume now automatically creates the KATA_DIRECT_VOLUME_ROOT_PATH directory if it does not exist 3.13.0 · Jan 2025 · source · release history
  • Drop QEMU log file support 3.1.0 · Mar 2023 · source · release history
  • Direct-assigned volume support (direct-assigned volumes) 2.5.0 · Aug 2022 · source · release history
  • Adds fsGroup support for directly assigned volumes to allow POSIX group ownership on mount 2.4.1 · May 2022 · source · release history
  • Add direct assigned volume support enabling volume managers like CSI to delegate block storage volume management to the kata agent 2.4.0 · Apr 2022 · source · release history
Agent API validation shipped Enables validation of the guest agent's state and capabilities via a dedicated CLI tool. 4 releases · 1 other source · first seen Oct 2020

Also counts toward: Command-line interface

release

  • Enables initrd boot capability for virtual machines using the Cloud Hypervisor backend. 2.4.0-alpha2 · Feb 2022 · source · release history
  • The govmm package is no longer a separate dependency; it is merged directly into the kata-containers repository. 2.4.0-alpha2 · Feb 2022 · source · release history
  • ProcessListContainer/ListProcesses APIs are removed from the runtime API 2.1.0 · May 2021 · source · release history
  • agent-ctl tool introduced (with GetGuestDetails subcommand) to validate the agent API 2.0.0 · Oct 2020 · source · release history

example

  • Verify the Kata agent is healthy after Helm installation. helm install kata kata/kata-containers --set kata.postInstallVerification.enabled=true 3.25.0 · Jan 2026 · source
Hypervisor config initdata shipped Allows setting initdata annotations directly in the hypervisor configuration. 5 releases · first seen Aug 2024

release

  • Adds initdata annotation support for remote configs in the Go runtime (runtime) 3.21.0 · Sep 2025 · source · release history
  • The annotation for passing through initdata confidential containers feature changed from io.katacontainers.config.runtime.cc_init_data to io.katacontainers.config.hypervisor.cc_init_data 3.20.0 · Aug 2025 · source · release history
  • Adds initdata annotation support for remote hypervisor in runtime-rs 3.19.0 · Jul 2025 · source · release history
  • initdata support for bare-metal and QEMU hypervisors 3.16.0 · Apr 2025 · source · release history
  • initdata annotation can now be set in the hypervisor config. 3.8.0 · Aug 2024 · source · release history
NVIDIA GPU guest extension support shipped Provides specialized tools and configuration for NVIDIA GPU workloads, including local repository support and DCGM exporter integration. 4 releases · first seen May 2024

release

  • Ship dcgm-exporter in the NVIDIA guest images 4.2.0 · Sep 2026 · source · release history
  • Ships dcgm-exporter in the NVIDIA GPU guest images. 4.2.0 · Sep 2026 · source · release history
  • Local CUDA repository support added for NVIDIA GPU extensions (nvgpu). 4.1.0 · Aug 2026 · source · release history
  • Deploys default RuntimeClass resources for NVIDIA GPU workloads via kata-deploy. 3.5.0 · May 2024 · source · release history
Core scheduling support shipped Enables core scheduling integration with containerd to optimize CPU resource isolation and performance. 4 releases · first seen Jun 2022

release

  • Places the runtime in the sandbox cgroup synchronously in runtime-rs, improving resource accounting. 4.1.0 · Aug 2026 · source · release history
  • runtime-rs now includes vCPU thread pinning support for finer control over VM CPU allocation. 3.30.0 · May 2026 · source · release history
  • Core scheduling support with containerd (core scheduling with containerd) 2.5.0 · Aug 2022 · source · release history
  • shim adds support for core scheduling 2.5.0-alpha2 · Jun 2022 · source · release history
Kubernetes Runtime Policy Generation Flexibility shipped Enhances the genpolicy utility with support for base64/raw output formats, sysfs permissions, and environment variable sourcing from labels. 3 releases · 1 other source · first seen Mar 2025

release

  • Adds genpolicy support for reading sysctls from PodSpec and environment defaults 3.15.0 · Mar 2025 · source · release history
  • Adds UpdateInterfaceRequest rules to genpolicy-settings allowing dynamic interface updates inside the container policy 3.15.0 · Mar 2025 · source · release history
  • Adds UpdateRoutesRequest rules to genpolicy-settings allowing dynamic route updates inside the container policy 3.15.0 · Mar 2025 · source · release history

example

  • Generate policy output directly as base64 or raw string instead of YAML for easier parsing in CI. genpolicy --base64-out -f policy.yaml > policy.b64 # or genpolicy --raw-out -f policy.yaml 3.27.0 · Feb 2026 · source
Guest-side image pulling shipped Allows container images to be pulled directly inside the guest environment using Kata Volumes or forced configuration, decoupling image availability from the host node. 4 releases · first seen Jul 2024

release

  • kata-deploy: Allow users to set experimental_force_guest_pull adds a helm chart option to force guest-side image pulling. 3.22.0 · Oct 2025 · source · release history
  • Adds runtime: add option to force guest pull to allow pulling images inside the guest environment 3.18.0 · Jun 2025 · source · release history
  • Supports pulling images in guest using Kata Volumes for CoCo in runtime-rs 3.18.0 · Jun 2025 · source · release history
  • Enables pulling encrypted container images via standard OCI registry calls without external credential helpers 3.7.0 · Jul 2024 · source · release history
CronJob policy generation shipped suggested Generates security policies for Kubernetes CronJob resources via the genpolicy utility. 3 releases · first seen Aug 2024

Suggested capability: Infrastructure-as-code security scanning. This is our guess, not confirmed.

release

  • Enables NFD (Node Feature Discovery) in the NVIDIA kata-deploy presets. 4.2.0 · Sep 2026 · source · release history
  • The cpu_nested_config override is removed from runtime-rs. 4.2.0 · Sep 2026 · source · release history
  • genpolicy gains support for Kubernetes CronJob resources. 3.8.0 · Aug 2024 · source · release history
Container Image Format Support Expansion shipped Adds support for Nydus standalone mode and enhanced EROFS with GPT VMDK snapshots in the Rust runtime. 3 releases · first seen Dec 2022

release

  • Support erofs snapshotter with gpt vmdk mode in runtime-rs 3.32.0 · Jun 2026 · source · release history
  • Nydus standalone mode support in runtime-rs 3.32.0 · Jun 2026 · source · release history
  • Add nydus to release artifacts for use as an image snapshotter 3.1.0-alpha1 · Dec 2022 · source · release history
Confidential Computing Hardware Support (AMD SNP) shipped Enables AMD Secure Nested Paging (SEV-SNP) for confidential computing workloads, deployed via kata-deploy runtime classes. 3 releases · first seen Mar 2025

Also counts toward: Kubernetes-native deployment

release

  • runtime-rs: Enhance TDX in qemu with new capabilities 3.29.0 · Apr 2026 · source · release history
  • kata-deploy now includes runtime-rs TDX / SNP runtimeclasses for deploying Intel Trust Domain Extensions and AMD Secure Nested Paging workloads. 3.26.0 · Jan 2026 · source · release history
  • Allows SNP_IDBlock configuration in runtime config to make Secure Nested Paging ID blocks adjustable 3.15.0 · Mar 2025 · source · release history
Guest network management shipped Provides CLI capabilities to manage network configurations, such as iptables rules, inside the guest environment. 3 releases · first seen Jun 2022

Also counts toward: Command-line interface

release

  • Adds guest network route updates via new route flags support in the kernel agent 3.15.0 · Mar 2025 · source · release history
  • kata-runtime iptables subcommand to get/set iptables rules in the guest via agent-ctl 2.5.0 · Aug 2022 · source · release history
  • agent-ctl introduces handle for iptables get/set 2.5.0-alpha2 · Jun 2022 · source · release history
Runtime compatibility and version checking shipped Provides a dedicated CLI utility to validate host architecture compatibility and verify release version integrity before deployment. 1 release · 2 other sources · first seen Dec 2022

release

  • Add kata-ctl CLI tool with architecture and version check capabilities (--check-version-only, arch checks) 3.1.0-alpha1 · Dec 2022 · source · release history

example

  • Verify the host architecture compatibility for the running kata runtime using the new tool. kata-ctl check arch 3.1.0-alpha1 · Dec 2022 · source
  • Check if the installed kata-ctl binary matches the expected release version before deploying. kata-ctl check release --check-version-only 3.1.0-alpha1 · Dec 2022 · source
genpolicy policy generation shipped genpolicy generates OPA policies for Kata Containers workloads, adding a default PATH when a container image environment lacks one, naming missing Secrets or ConfigMaps in error output, and verifying guest-pulled image references. 2 releases · first seen Oct 2026

release

  • Improves genpolicy by adding a default PATH when the container image environment lacks one and by naming the missing Secret or ConfigMap when an env source is absent. 4.3.0 · Oct 2026 · source · release history
  • Verifies guest-pulled image references in genpolicy. 4.3.0 · Oct 2026 · source · release history
kata-deploy host device provisioning and NFD detection shipped kata-deploy can provision host devices for rootless VMMs and detect external Node Feature Discovery (NFD) labels, and restricts containerd pod_annotations to per-installation configuration while honoring imagePullSecrets on kubectl-image hook Jobs. 2 releases · first seen Oct 2026

release

  • Adds kata-deploy support to provision host devices for rootless VMMs and to detect external Node Feature Discovery (NFD) by label. 4.3.0 · Oct 2026 · source · release history
  • Improves kata-deploy by restricting containerd pod_annotations to the per-installation configuration and honoring imagePullSecrets on kubectl-image hook Jobs. 4.3.0 · Oct 2026 · source · release history
Runtime class filtering in policy generation shipped Filters generated security policies by Kubernetes RuntimeClassName. 2 releases · first seen Jun 2024

release

  • The disable_block_device_use option is removed from runtime-rs as it was unsupported — configs referencing it will need to be updated. 4.2.0 · Sep 2026 · source · release history
  • Adds genpolicy ability to filter by RuntimeClassName (new runtimeClassName filter in genpolicy) 3.6.0 · Jun 2024 · source · release history
TLS configuration capabilities verified Provides CLI options for configuring minimum TLS version and cipher suites to secure communication. 2 other sources · first seen Sep 2026

command line

  • --tls-min-version — Minimum TLS version (VersionTLS12, VersionTLS13). Defaults to VersionTLS12 when TLS is enabled. 4.2.0 · Sep 2026 · command-line history
  • --tls-cipher-suites — Comma-separated list of TLS cipher suite names (IANA format). Applies to TLS 1.2 and below. 4.2.0 · Sep 2026 · command-line history
L3 forwarding network model shipped Adds support for an L3 forwarding network topology option in the Rust runtime. 2 releases · first seen Aug 2026

release

  • Adds L3 forwarding network model for runtime-rs, enabling an additional network topology option. 4.1.0 · Aug 2026 · source · release history
  • runtime-rs introduces the L3 forwarding network model for sandbox connectivity 4.1.0 · Aug 2026 · source · release history
Non-root VMM execution shipped Enables the Virtual Machine Monitor process to run with reduced privileges (non-root mode) to minimize the attack surface. 2 releases · first seen Nov 2025

release

  • Disables QEMU features and devices by default to reduce the attack surface. 4.1.0 · Aug 2026 · source · release history
  • Enables CLH VMM process to run in non-root mode within the runtime-rs subsystem 3.23.0 · Nov 2025 · source · release history
OpenVMM hypervisor support shipped Enables the use of OpenVMM as a supported virtual machine monitor within the cyber toolchain. 2 releases · first seen Aug 2026

release

  • runtime-rs now supports the OpenVMM virtual machine monitor as a backend option 4.1.0 · Aug 2026 · source · release history
  • Adds OpenVMM hypervisor support in runtime-rs. 4.1.0 · Aug 2026 · source · release history
Confidential Guest VFIO Device Assignment Isolation shipped Enforces iommufd for strict IOMMU isolation when assigning devices to confidential guests. 2 releases · first seen Mar 2025

release

  • The shim now enforces iommufd for confidential guest VFIO device assignment, ensuring strict IOMMU isolation for secure VMs. 3.26.0 · Jan 2026 · source · release history
  • Enables IOMMUFD GPU support in QEMU via experimental updates and module signing 3.15.0 · Mar 2025 · source · release history
SGX hardware support shipped Enables Intel Software Guard Extensions (SGX) for confidential computing workloads via default kernel and supported hypervisors. 2 releases · first seen Apr 2022

release

  • runtime-go | kata-deploy: Add Arm CCA confidential Guest Support enables support for Arm Confidential Computing Architecture. 3.22.0 · Oct 2025 · source · release history
  • Add support for Intel® Software Guard Extensions (Intel® SGX) as part of the default kernel with support added to Cloud Hypervisor and QEMU drivers 2.4.0 · Apr 2022 · source · release history
Confidential container policy framework shipped Integrates the CNCF Confidential Container Runtime policy framework for evaluating policies on confidential workloads. 2 releases · first seen Jul 2024

release

  • Adds CoCo annotations support for ConfidentialGuests in qemu runtime 3.21.0 · Sep 2025 · source · release history
  • Introduces support for the CNCF Confidential Container Runtime (coco) policy framework in the Go kata-runtime via the DAN (Device Access Network) implementation 3.7.0 · Jul 2024 · source · release history
Tarball unpacking and compression support shipped Extends cyber tooling deployment utilities with support for modern compression formats (xz, zst) for efficient tarball handling and extraction. 2 releases · first seen Sep 2025

release

  • Adds zst suffix handling to kata-manager for tarball unpacking 3.21.0 · Sep 2025 · source · release history
  • Adds xz and zst suffix support for the kata tarball in kata-deploy local-build 3.21.0 · Sep 2025 · source · release history
Guest memory and swap management shipped Enables memory-specific agent operations and guest-side swap configuration via the cyber tooling to optimize memory utilization and handling inside the guest environment. 2 releases · first seen Jan 2025

release

  • Adds AddGuestSwap configuration option to confidential_guest.toml.in for enabling guest-side swap support 3.15.0 · Mar 2025 · source · release history
  • Adds mem-agent support to kata-containers to enable memory-specific agent operations 3.13.0 · Jan 2025 · source · release history
Agent capability extensions shipped The agent supports unsealing sealed secret environment variables during exec requests, reporting cgroup v2 CPU throttling time, and falling back to fsmount when overlay options exceed 4K. 1 release · first seen Oct 2026

release

  • Adds agent capabilities to unseal sealed secret environment variables during exec requests, report cgroup v2 CPU throttling time, and fall back to fsmount when overlay options exceed 4K. 4.3.0 · Oct 2026 · source · release history
Webhook minimum memory enforcement shipped The kata-webhook can enforce a minimum memory limit on sandbox workloads. 1 release · first seen Oct 2026

release

  • Adds ability to enforce a minimum memory limit in the kata-webhook. 4.3.0 · Oct 2026 · source · release history
VM template generation for OpenVMM shipped Adds the capability to create and manage VM templates specifically optimized for the OpenVMM hypervisor. 1 release · first seen Aug 2026

release

VM Template Management for Cloud Hypervisor shipped Adds support for creating and managing VM templates specifically within the Cloud Hypervisor environment via runtime-rs. 1 release · first seen Aug 2026

release

  • Adds Cloud Hypervisor VM template support in runtime-rs. 4.1.0 · Aug 2026 · source · release history
Measured rootfs build targets shipped Provides Makefile targets to construct a measured rootfs for integrity verification and attestation. 1 other source · first seen Jan 2026

example

  • Build a measured rootfs using the new Makefile targets. cd src/runtime-rs make measured-rootfs # Uses dedicated configuration keys 3.25.0 · Jan 2026 · source
VM template management shipped Provides CLI subcommands for creating and managing VM templates to optimize startup time and resource usage. 1 release · first seen Nov 2025

Also counts toward: Command-line interface

release

  • Adds kata-ctl vm-template factory subcommands for VM template management 3.23.0 · Nov 2025 · source · release history
Confidential sealed secrets volume mount shipped Enables mounting confidential sealed secrets as a volume inside the guest environment. 1 release · first seen Oct 2024

release

Trusted image storage shipped Introduces support for storing container images in a trusted manner within the cyber tooling. 1 release · first seen Aug 2024

release

GPU rootfs initrd build targets shipped Provides build targets for generating GPU-specific rootfs initrd images. 1 release · first seen Jun 2024

release

  • Adds build targets for GPU rootfs initrd/image via gpu: Add build targets for GPU rootfs initrd/image 3.6.0 · Jun 2024 · source · release history
Guest agent policy evaluation shipped Replaces the OPA policy engine with Regorus to evaluate security policies inside the kata-agent. 1 release · first seen May 2024

release

  • Integrates regorus as the new policy engine in kata-agent, replacing OPA. 3.5.0 · May 2024 · source · release history
Stratovirt VMM support shipped Supports Stratovirt as a lightweight virtual machine monitor within the cyber toolchain. 1 release · first seen Mar 2024

release

  • Add StratoVirt as a supported lightweight VMM for Kata containers 3.3.0 · Mar 2024 · source · release history
Guest agent SELinux support shipped Enables SELinux policy enforcement and context management within guest containers via the runtime agent. 1 release · first seen Dec 2022

release

  • Add SELinux support in the agent for guest containers (requires OSBuilder images and kernel configs) 3.1.0-alpha1 · Dec 2022 · source · release history
VMM SELinux configuration shipped Allows configurable SELinux contexts for the virtual machine monitor. 1 release · first seen Apr 2022

release

  • Make VMM SELinux configurable via a new configuration option 2.4.0 · Apr 2022 · source · release history
Agent protocol (ttRPC) shipped Simplifies the agent wire format by switching from gRPC to ttRPC. 1 release · first seen Oct 2020

release

  • Agent protocol switched from gRPC to ttRPC, simplifying the agent wire format 2.0.0 · Oct 2020 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for kata-containers, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail kata-containers puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Show

61 entries

  1. October 20261
  2. September 20261
  3. August 20262
  4. July 20265
  5. June 20261
  6. May 20264
  7. April 20262
  8. March 20261
  9. February 20262
  10. January 20263
  11. December 20251
  12. November 20251
  13. October 20251
  14. September 20252
  15. August 20251
  16. July 20251
  17. June 20251
  18. May 20251
  19. April 20251
  20. March 20251
  21. February 20251
  22. January 20251
  23. December 20241
  24. November 20241
  25. October 20241
  26. September 20241
  27. August 20241
  28. July 20241
  29. June 20241
  30. May 20241
  31. April 20241
  32. March 20241
  33. October 20231
  34. March 20231
  35. December 20221
  36. October 20221
  37. September 20221
  38. August 20221
  39. June 20221
  40. May 20221
  41. April 20221
  42. March 20221
  43. February 20221
  44. November 20211
  45. May 20212
  46. April 20211
  47. October 20201
    Show

    61 entries

    Project health

    Issue, contributor and maintainer activity in kata-containers/kata-containers, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 122 +27 vs prior 12 months
    2. Maintainers 7 +2 joined · −11 left, last 12 months
    3. Bus factor 2 committers behind half the commits
    4. Community-filed 87% of issues opened, last 12 months
    5. Median time to close 3.9 years first maintainer reply 4.3 days
    6. Open backlog 997 of 6,115 issues ever filed
    1. Issues opened / month 8 · 1 communitymaintainers
    2. Open backlog 997
    3. Contributors / month 20
    4. Commits / month 96
    5. Stars 8,752
    Issue themes, last 12 months
    • bugs 41%
    • features 24%
    • questions 7%
    • other 28%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →