Repository navigation
Conversation
ImportZone can restore a snapshot as the zone of a Kubernetes pod, leaving it paused until the pod's runtime claims it with ClaimRestoredZone, starts it with StartRestoredZone and binds each workload to its container with AdoptWorkload.
|
The latest Buf updates on your PR. Results from workflow Buf CI / buf (pull_request).
|
The restore claim is an opaque string with annotations the daemon does not read, and the runtime tells StartRestoredZone where each mount is bound, so the control API carries nothing about any orchestrator.
azenla
marked this pull request as ready for review
October 18, 2026 23:22
marly-edera
approved these changes
Oct 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the control calls for restoring a snapshot into a zone whose host mounts a runtime binds before the guest runs. Nothing in them names an orchestrator.
ImportZoneStart.restore { claim, annotations }holds the imported zone, paused and with its host mounts unbound. The claim is an opaque string and the annotations are kept for whoever claims the zone; the daemon reads neither.ClaimRestoredZone(claim)returns the zone, the annotations, and each running workload with its annotations and mounts. A mount carriesrecorded_host_path, which is only a hint: the daemon never binds it.StartRestoredZone(zone_id, bindings[], annotations[])carries one binding per mount, either a host path or a placeholder, and the annotations to set on the zone. The daemon refuses a request that leaves a mount unbound or names one that does not exist.AdoptWorkloadbinds a restored workload to the container a runtime created for it, with that container's own mounts and annotations.The design is in the draft protect PR that uses these calls (docs/specs/pod-restore.md).