IMPFirecracker microVMs as first-class Kubernetes resources

Run Firecracker microVMs on Kubernetes with CRDs for networking, snapshots, migration, and warm pools.

Quickstart

Read Architecture

Kubernetes-Native VM API

Manage VM lifecycle through CRDs like ImpVM, ImpNetwork, ImpVMSnapshot, ImpVMMigration, and ImpWarmPool.

Performance + Isolation

Run Firecracker VMs with operator lifecycle, metrics, and health checks.

Networking that Fits Reality

Cilium-first networking with practical fallback paths for non-Cilium CNIs.

Built for Platform Teams

Operator and node agent split keeps control logic and node operations cleanly scoped, with optional imp-sandbox add-on for isolated tenants.

Alpha v0.10.1 — APIs may break; see Manual → Install

v0.10.1 is the current Imp release. The runner-pool documentation now covers the GitHub App and just-in-time (JIT) runner path, immutable runner image layers, and the boundary between source-backed behaviour and live evidence.

imp quickstart // shell

bash

helm upgrade --install imp ./charts/imp -n imp-system --create-namespace
kubectl get impvm -n default
kubectl describe impvm quick-vm -n default

Why IMP

Declare VM lifecycle

Use manifests for VM lifecycle. Avoid per-host scripts.

Inspect runtime state

Use metrics and status fields to check lifecycle state, latency, and health.

Use the same API across environments

Use the same CRDs in local Kind clusters and production, including migration and warm-pool workflows.

Optional Sandbox

Add imp-sandbox for multi-tenant isolation with standard or hard tenancy and gateway controls. Read the sandbox docs →