Skip to content
Vol. 1 · Ed. 2026
CyberGlossary
Entry № 653

Kata Containers

Reviewed byCybersecurity entrepreneur & security researcher

What is Kata Containers?

Kata ContainersKata Containers is an open-source runtime that wraps each container or Kubernetes pod in a lightweight virtual machine to provide hardware-level isolation between workloads.


Kata Containers launches a minimal Linux guest inside a hypervisor (QEMU, Cloud Hypervisor, or AWS Firecracker) for every container or pod. Each workload gets its own guest kernel, so a kernel-level exploit or container escape in one tenant cannot reach the host or sibling workloads — a stronger boundary than the shared-kernel model of runc, where namespaces, cgroups and seccomp are the only walls. Kata implements the OCI and Kubernetes CRI interfaces through containerd/CRI-O shims, so existing images and Pod specs run unchanged; operators select it per workload with a Kubernetes RuntimeClass (kata-qemu, kata-fc), sending only untrusted pods through the VM path. The cost is higher boot latency and memory overhead than runc; the gain is VM-grade isolation for multi-tenant or untrusted code. Compared with gVisor, which intercepts syscalls in a userspace kernel, Kata uses real virtualization hardware (VT-x/AMD-V).

The project formed in December 2017 by merging Intel's Clear Containers with Hyper.sh's runV, reaching its 1.0 release in May 2018; it is hosted by the OpenInfra Foundation (formerly the OpenStack Foundation) and supports x86-64, Arm and IBM Z. Kata is also the runtime foundation of the Confidential Containers (CoCo) project, which boots each pod inside a hardware TEE (Intel TDX, AMD SEV-SNP) and adds an in-guest attestation agent and image-management stack, extending isolation into confidential-computing use cases such as protecting AI workloads on untrusted cloud hosts.

flowchart TD
  POD[Kubernetes pod spec] --> RC{RuntimeClass?}
  RC -->|runc trusted| RUNC[Shared host kernel<br/>namespaces + seccomp]
  RC -->|kata untrusted| SHIM[containerd-shim-kata]
  SHIM --> HV[Hypervisor: QEMU /<br/>Cloud Hypervisor / Firecracker]
  HV --> VM[Lightweight VM<br/>own guest kernel]
  VM --> AGENT[kata-agent runs<br/>the container]
  VM -.CoCo.-> TEE[Boot inside TEE<br/>TDX / SEV-SNP + attestation]

● Examples

  1. 01

    A serverless platform isolating tenant functions in Firecracker microVMs via Kata.

  2. 02

    A Kubernetes RuntimeClass routing untrusted pods to kata-qemu while trusted pods stay on runc.

● Frequently asked questions

What is Kata Containers?

Kata Containers is an open-source runtime that wraps each container or Kubernetes pod in a lightweight virtual machine to provide hardware-level isolation between workloads. It belongs to the Cloud Security category of cybersecurity.

What does Kata Containers mean?

Kata Containers is an open-source runtime that wraps each container or Kubernetes pod in a lightweight virtual machine to provide hardware-level isolation between workloads.

How do you defend against Kata Containers?

Defences for Kata Containers typically combine technical controls and operational practices, as detailed in the full definition above.

What are other names for Kata Containers?

Common alternative names include: Kata, Kata runtime.

● Related terms