Notable changes to Snapshot, in the format of Keep a Changelog. Versions follow Semantic Versioning; see RELEASE.md for how releases are cut and which versions receive security fixes.
Entries describe what changed for someone operating Snapshot — new capabilities, behavior changes, and anything requiring action on upgrade. CRD changes and changes to checkpoint or restore semantics are called out explicitly, because they affect checkpoints that already exist. The full commit-level history for each release is on its GitHub release page.
PodSnapshotContent.status.sourcerecords what a checkpoint was captured on: the source node's name, architecture and kernel version, the captured container's image, image digest and CPU and memory limits, and the NVIDIA driver version and GPU models the capture could see. Informational only — restore compatibility still compares the artifact's manifest. CRD change; populated for captures that reachReadyafter the upgrade, so a content alreadyReadybefore it is not backfilled.
0.1.0 - 2026-09-06
First release. Snapshot checkpoints a fully initialized GPU pod — running process, CPU and GPU memory — and restores that state on another compatible node, cutting cold-start time for large inference workloads.
PodSnapshot,PodSnapshotContent, andSnapshotJobcustom resources, and therestore-fromannotation for programmatic restore.- Cluster operator that reconciles the custom resources, and a node-level agent
DaemonSet that drives CRIU and
cuda-checkpointagainst live processes. snapshotctlfor lower-level checkpoint and restore from a pod manifest.- Helm chart published as an OCI artifact to GHCR, with CRDs upgraded from an init container so a chart upgrade cannot leave them stale.
- Restore Pod contract covering the control volume, startup gate, seccomp
profile, and the
SNAPSHOT_CONTROL_DIRenvironment variable. - Framework guides with runnable manifests for vLLM, SGLang, and TensorRT-LLM.
- Corresponding source and third-party attribution shipped inside both images
under
/legal.
Checkpoint and restore require compatible GPU and driver versions between the source and target node. See Limitations for the current boundaries.
0.1.0-rc2 - 2026-09-03
Release candidate for 0.1.0.
0.1.0-rc.1 - 2026-09-01
Release candidate for 0.1.0.
0.1.0-alpha.1 - 2026-08-16
First tagged build, published to validate the release pipeline.