Introduce WG Checkpoint Restore #8508

adrianreber · 2025-07-03T13:33:14Z

As described in sig-wg-lifecycle.md this PR is the next step after sending an email to dev@kubernetes.io about the creation of the Working Group Checkpoint Restore.

CC: @rst0git, @viktoriaas, @xhejtman

k8s-ci-robot · 2025-07-03T13:33:24Z

Welcome @adrianreber!

It looks like this is your first PR to kubernetes/community 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/community has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

k8s-ci-robot · 2025-07-03T13:33:25Z

Hi @adrianreber. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions 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.

OWNERS_ALIASES

kannon92 · 2025-07-10T18:31:17Z

/ok-to-test

kannon92 · 2025-07-15T02:42:37Z

Looking at #8519,

I see that we are missing a charter.

adrianreber · 2025-07-15T06:34:13Z

Looking at #8519,

I see that we are missing a charter.

In https://github.com/kubernetes/community/blob/master/sig-wg-lifecycle.md#GitHub is says to add a charter once this initial PR has been merged. That's why is skipped it.

SergeyKanzhelev · 2025-07-18T17:40:53Z

sigs.yaml

+    the integration of Checkpoint/Restore functionality into Kubernetes.
+
+  charter_link: charter.md
+  stakeholder_sigs:


sig auth may have a big say in security of this whole restoration pipeline

Thank you for pointing this out! Security is definitely an important topic that we need to discuss with sig-auth, both for the checkpoint API and the restoration pipeline. The following paper and master thesis describe our recent work on this topic:

Towards Efficient End-to-End Encryption for Container Checkpointing Systems

Improving Checkpoint/Restore Functionality in Kubernetes

I added sig auth to the list of stakeholder sigs

this showed up in the sig-auth meeting, we may have missed the discussion around this WG

if this WG is contemplating taking state from a running pod / saving it / letting it be consumed on another node or from another pod or another namespace, then sig-auth is definitely interested in making sure the permissions model around that exists and is ~consistent with similar things Kubernetes does elsewhere (like PVC / snapshots)

We're happy to consult on that, I'm not sure our awareness / involvement rises to the level of sponsoring the WG :)

cc @kubernetes/sig-auth-leads

nod.. definitely needs an extra level of security due to customer data being serialized and available in the checkpoint, esp if not encrypted, but also due to windows of opportunity to do transactions/data manipulation.. then "undo" them by restoring a checkpoint

sigs.yaml

lujinda · 2025-09-14T14:01:32Z

Is there a slack channel where we can discuss C/R related ideas? Thanks

adrianreber · 2025-09-14T14:04:38Z

Is there a slack channel where we can discuss C/R related ideas? Thanks

You are not the first to ask. We kind of are waiting for the proposal to be accepted to have a slack channel. Not sure if there is a another way to have a slack channel without having the proposal merged.

rst0git · 2025-09-15T10:25:33Z

Is there a slack channel where we can discuss C/R related ideas?

@lujinda Please reach out to us in the Kubernetes slack. You can find Viktoria, Adrian, and myself there :)

BenTheElder

I can't tell if this has been raised to all the relevant SIGs yet (via their mailinglist, slack, meetings or similar, particularly to the leads to +1)

Otherwise I think this is looking pretty good ...

adrianreber · 2025-09-25T18:02:31Z

@rst0git @viktoriaas are currently trying to bring this WG up in all the mentioned SIGs.

Which SIGs haven't been officially informed about this?

viktoriaas · 2025-09-25T18:13:05Z

@rst0git @viktoriaas are currently trying to bring this WG up in all the mentioned SIGs.

Which SIGs haven't been officially informed about this?

We attended SIG Node (16.9) and SIG Scheduling (18.9.), so SIG API Machinery, SIG Auth, SIG Apps are left.

wg-checkpoint-restore/charter.md

BenTheElder · 2025-10-01T20:26:44Z

For SIG Apps I think we have @janetkuo and @soltysh on this thread, cc @kow3ns.

For auth @ritazh @liggitt have commented here but I think we also need to discuss with others, x-ref https://github.com/kubernetes/community/pull/8508/files#r2274401485

Going to the meeting is a good approach, but you could also try raising to the mailinglists / slacks for earlier feedback.

kow3ns · 2025-10-13T16:40:36Z

After hearing the presentation SIG Apps is +1. We don't anticipate this work, in the near term, impacting the in tree components that fall under SIG Apps. However, we think we can be advocates for users that run workloads and applications that use the infrastructure to ensure that it meets their use cases.

aojea · 2025-10-15T15:20:30Z

wg-checkpoint-restore/README.md

+* [SIG Apps](/sig-apps)
+* [SIG Auth](/sig-auth)
+* [SIG Node](/sig-node)
+* [SIG Scheduling](/sig-scheduling)


I see SIG Apps +1 on the comments, do we have +1 from the other 3 SIGs in the comments

@haircommander Are you the right person to +1 from SIG Node?

@viktoriaas Who at SIG scheduling did you talk to. Can they +1 here?

@rst0git plans to present at the SIG-Auth meeting on Wednesday, October 22nd.

Who at SIG scheduling did you talk to. Can they +1 here?

@dom4ha As a follow-up on the discussion we had at the SIG-Scheduling meeting on September 18th, would you be able to add +1 for our working group?

I think an ack from sig-scheduling is still needed.

+1 from sig-scheduling. We discussed it on our sig meeting and looking forward for any integration with the scheduler logic.

Co-authored-by: Viktória Spišaková <spisakova@ics.muni.cz> Co-authored-by: Antonio Ojea <antonio.ojea.garcia@gmail.com> Co-authored-by: Sergey Kanzhelev <S.Kanzhelev@live.com> Signed-off-by: Adrian Reber <areber@redhat.com>

neolit123 · 2025-10-22T18:43:13Z

wg-checkpoint-restore/charter.md

+- SIG Node
+- SIG Scheduling
+- SIG Auth
+- SIG Apps


is SIG networking a stakeholder, given details around checkpoint/restoring the network of a container?

There was some discussion above #8508 (comment)

adrianreber · 2025-10-24T08:45:30Z

At this point we presented our idea at all possibly involved SIGs. (I think). Anything missing to create this WG?

BenTheElder · 2025-10-28T18:42:26Z

cc @kubernetes/steering-committee I think all of the SIG ACKs are done and there don't seem to be suggestions / concerns raised from the related SIGs.

/lgtm
/approve
/hold

Holding for review + ACK from other steering members.

k8s-ci-robot · 2025-10-28T18:42:39Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adrianreber, BenTheElder

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

~~OWNERS~~ [BenTheElder]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

aojea · 2025-10-28T19:17:12Z

+1 (steering)

pacoxu

/lgtm
(steering)

k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Jul 3, 2025

k8s-ci-robot requested review from deads2k and macsko July 3, 2025 13:33

k8s-ci-robot added sig/node Categorizes an issue or PR as relevant to SIG Node. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. labels Jul 3, 2025

github-project-automation bot added this to SIG Scheduling Jul 3, 2025

github-project-automation bot moved this to Needs Triage in SIG Scheduling Jul 3, 2025

k8s-ci-robot added the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Jul 3, 2025

adrianreber mentioned this pull request Jul 3, 2025

Checkpointing API kubernetes/enhancements#5091

Open

6 tasks

haircommander reviewed Jul 8, 2025

View reviewed changes

OWNERS_ALIASES Show resolved Hide resolved

adrianreber force-pushed the 2025-07-03-wg-cr branch from 33e97fb to abc1c26 Compare July 9, 2025 12:15

kannon92 reviewed Jul 10, 2025

View reviewed changes

OWNERS_ALIASES Show resolved Hide resolved

k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jul 10, 2025

adrianreber mentioned this pull request Jul 17, 2025

REQUEST: New membership for adrianreber kubernetes/org#5706

Closed

11 tasks

SergeyKanzhelev reviewed Jul 18, 2025

View reviewed changes

sigs.yaml Outdated Show resolved Hide resolved

adrianreber force-pushed the 2025-07-03-wg-cr branch from abc1c26 to 8bc6968 Compare July 20, 2025 15:15

k8s-ci-robot added committee/steering Denotes an issue or PR intended to be handled by the steering committee. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jul 20, 2025

helayoty moved this from Needs Triage to Backlog in SIG Scheduling Sep 9, 2025

helayoty moved this from Backlog to Needs Review in SIG Scheduling Sep 9, 2025

k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 9, 2025

BenTheElder reviewed Sep 25, 2025

View reviewed changes

rst0git reviewed Oct 1, 2025

View reviewed changes

wg-checkpoint-restore/charter.md Outdated Show resolved Hide resolved

adrianreber force-pushed the 2025-07-03-wg-cr branch from da35847 to 69c0f4f Compare October 8, 2025 15:28

k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 8, 2025

This was referenced Oct 14, 2025

Unable to restore a process tree with a child in a separate user namespace checkpoint-restore/criu#2778

Open

Proposal: Support flexible storage for checkpoint/restore containerd/containerd#12296

Open

aojea reviewed Oct 15, 2025

View reviewed changes

Introduce WG Checkpoint Restore

cef6a0d

Co-authored-by: Viktória Spišaková <spisakova@ics.muni.cz> Co-authored-by: Antonio Ojea <antonio.ojea.garcia@gmail.com> Co-authored-by: Sergey Kanzhelev <S.Kanzhelev@live.com> Signed-off-by: Adrian Reber <areber@redhat.com>

adrianreber force-pushed the 2025-07-03-wg-cr branch from 69c0f4f to cef6a0d Compare October 15, 2025 15:34

neolit123 reviewed Oct 22, 2025

View reviewed changes

k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 28, 2025

k8s-ci-robot assigned BenTheElder Oct 28, 2025

k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 28, 2025

k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 28, 2025

pacoxu reviewed Oct 29, 2025

View reviewed changes

k8s-ci-robot assigned pacoxu Oct 29, 2025

Uh oh!

Introduce WG Checkpoint Restore #8508

Are you sure you want to change the base?

Introduce WG Checkpoint Restore #8508

Conversation

adrianreber commented Jul 3, 2025

Uh oh!

k8s-ci-robot commented Jul 3, 2025

Uh oh!

k8s-ci-robot commented Jul 3, 2025

Uh oh!

Uh oh!

Uh oh!

kannon92 commented Jul 10, 2025

Uh oh!

kannon92 commented Jul 15, 2025

Uh oh!

adrianreber commented Jul 15, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

rst0git Jul 19, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mikebrow Sep 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

lujinda commented Sep 14, 2025

Uh oh!

adrianreber commented Sep 14, 2025

Uh oh!

rst0git commented Sep 15, 2025

Uh oh!

BenTheElder left a comment

Choose a reason for hiding this comment

Uh oh!

adrianreber commented Sep 25, 2025

Uh oh!

viktoriaas commented Sep 25, 2025

Uh oh!

Uh oh!

BenTheElder commented Oct 1, 2025

Uh oh!

kow3ns commented Oct 13, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

adrianreber commented Oct 24, 2025

Uh oh!

BenTheElder commented Oct 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

k8s-ci-robot commented Oct 28, 2025

Uh oh!

aojea commented Oct 28, 2025

Uh oh!

pacoxu left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

rst0git Jul 19, 2025 •

edited

Loading

mikebrow Sep 9, 2025 •

edited

Loading

BenTheElder commented Oct 28, 2025 •

edited

Loading