cri: remove restore in CreateContainer - #13871
Conversation
There was a problem hiding this comment.
Pull request overview
Removes the (previously deprecated) CRI CreateContainer checkpoint-restore path, eliminating the container-restore control flow and associated deprecation plumbing. This aligns CRI restore support with the newer Pod-level direction (KEP-5823 / RestorePod) referenced in the PR description.
Changes:
- Remove CRI CreateContainer-based checkpoint restore code paths (CreateContainer + StartContainer) and related status/deprecation wiring.
- Delete now-obsolete checkpoint-restore tests/scripts and the corresponding CI job step.
- Mark the deprecation entry as completed in
RELEASES.md.
Reviewed changes
Copilot reviewed 14 out of 14 changed files in this pull request and generated no comments.
Show a summary per file
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
09c1dcd to
7e223f1
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 14 out of 14 changed files in this pull request and generated no new comments.
Comments suppressed due to low confidence (1)
.github/workflows/ci.yml:560
- The CI step name still says "Checkpoint/Restore Disable via CRI", but this workflow no longer runs any restore coverage (and the invoked script now only tests checkpoint behavior). Renaming the step will avoid confusion when reading CI logs and job summaries.
- if: matrix.os != 'ubuntu-24.04-arm'
name: Checkpoint/Restore Disable via CRI
env:
|
Could you explain why the container snapshot feature was removed? @samuelkarp |
Remove support for restoring checkpoint data during CreateContainer, which was previously deprecated in v2.3. Assisted-by: Antigravity Signed-off-by: Samuel Karp <samuelkarp@google.com>
7e223f1 to
91be73b
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 14 out of 14 changed files in this pull request and generated no new comments.
Comments suppressed due to low confidence (2)
internal/cri/server/container_create.go:135
- With checkpoint-restore support removed from CreateContainer, a caller that still passes a checkpoint archive path will now fail later with an image-store "failed to resolve image" error even when the file exists, which is harder to diagnose. Consider explicitly detecting the (previously supported) archive-path case and returning a clearer error pointing users to RestorePod (KEP-5823).
image, err := c.LocalResolve(config.GetImage().GetImage())
if err != nil {
return nil, fmt.Errorf("failed to resolve image %q: %w", config.GetImage().GetImage(), err)
.github/workflows/ci.yml:559
- This workflow step name still mentions "Checkpoint/Restore", but the restore path and related CI coverage were removed in this PR. Renaming the step makes CI output match what is actually being exercised.
name: Checkpoint/Restore Disable via CRI

Remove support for restoring checkpoint data during CreateContainer, which was previously deprecated in v2.3.
This will conflict with #13822. If this PR lands first, #13822 will need to add back relevant code (and would be a good time to re-review it). If that one lands first, I can update this PR.