Add pod-level checkpoint/restore support to crictl (KEP-5823)#1997
Add pod-level checkpoint/restore support to crictl (KEP-5823)#1997adrianreber wants to merge 3 commits into
Conversation
Import github.com/checkpoint-restore/checkpointctl at commit 06e23e6d1f24 to provide pod checkpoint metadata types needed for pod-level checkpoint/restore (KEP-5823). Generated with Claude Code (https://claude.ai/code) Signed-off-by: Adrian Reber <areber@redhat.com>
This is part of KEP-5823: Pod-Level Checkpoint/Restore. Add two new crictl commands for pod-level checkpoint/restore: - checkpointp: Checkpoint one or more running pods to an archive file specified via --export. Sends CheckpointPodRequest to the CRI runtime. - restorep: Restore a pod from a checkpoint image or archive. Supports optional --config for providing a PodSandboxConfig JSON file, and --label/--annotation flags for setting labels and annotations on the restored pod sandbox. Update the vendored CRI API to include the new CheckpointPod and RestorePod RPCs: - CheckpointPodRequest with PodSandboxId and Path fields - CheckpointPodResponse (empty) - RestorePodRequest with Path, Config (PodSandboxConfig), and RuntimeHandler fields - RestorePodResponse with PodSandboxId Generated with Claude Code (https://claude.ai/code) Signed-off-by: Adrian Reber <areber@redhat.com>
Build checkpointp CLI flags dynamically from metadata.SupportedCheckpointOptions instead of hardcoding them. This passes options via the CheckpointPodRequest.Options map so that new checkpoint options added in checkpointctl automatically appear as crictl flags. Generated with Claude Code (https://claude.ai/code) Signed-off-by: Adrian Reber <areber@redhat.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: adrianreber The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
PR needs rebase. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
This adds two new crictl commands:
added upstream automatically appear as crictl flags.
sandbox.
The CRI API changes (CheckpointPodRequest/CheckpointPodResponse, RestorePodRequest/RestorePodResponse) are manually vendored from the Kubernetes repository until the upstream changes are released.
Also see:
Changes