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 [email protected] 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:24Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: adrianreber
Once this PR has been reviewed and has the lgtm label, please assign saschagrunert for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

OWNERS

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

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:30:39Z

OWNERS_ALIASES

@@ -130,6 +130,11 @@ aliases:
    - mwielgus
    - soltysh
    - swatisehgal
+  wg-checkpoint-restore-leads:


Is everyone on this list a kubernetes org member?

#8508 (comment)

Unfortunately not. I talked with @haircommander and he would be willing to sponsor me. Still looking for a sponsor from another company.

https://github.com/kubernetes/community/blob/master/community-membership.md#requirements

Sponsored by 2 reviewers. Note the following requirements for sponsors:

Sponsors must have close interactions with the prospective member - e.g. code/design/proposal review, coordinating on issues, etc.

Sponsors must be reviewers or approvers in at least one OWNERS file within one of the Kubernetes GitHub organizations*.

Sponsors must be from multiple member companies to demonstrate integration across community.

Are there any other existing community members interested in helping run this effort?

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

SergeyKanzhelev · 2025-07-18T17:43:14Z

sigs.yaml

+    This working group aims to provide a central location for the community to discuss
+    the integration of Checkpoint/Restore functionality into Kubernetes.
+
+  charter_link: charter.md


is charter included into this PR?

now it is, I didn't add it initially as the lifecycle document mentions that it is added later, but looking at the WG PRs it seems to be common to have a charter in the initial PR.

Signed-off-by: Adrian Reber <[email protected]>

adrianreber · 2025-07-20T15:15:59Z

I added a charter based on the content we sent to the mailing list.

k8s-ci-robot · 2025-07-20T15:16:01Z

The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the kubernetes org. You can then trigger verification by writing /verify-owners in a comment.

adrianreber
- User is not a member of the org. Satisfy at least one of these conditions to make the user trusted.
rst0git
- User is not a member of the org. Satisfy at least one of these conditions to make the user trusted.
viktoriaas
- User is not a member of the org. Satisfy at least one of these conditions to make the user trusted.

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

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

Open

11 tasks

SergeyKanzhelev reviewed Jul 18, 2025

View reviewed changes

Introduce WG Checkpoint Restore

8bc6968

Signed-off-by: Adrian Reber <[email protected]>

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

enj added this to SIG Auth Jul 21, 2025

enj moved this to Needs Triage in SIG Auth Jul 21, 2025

adrianreber marked this pull request as ready for review July 22, 2025 16:02

k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 22, 2025

k8s-ci-robot requested review from dom4ha and fedebongio July 22, 2025 16:02

Introduce WG Checkpoint Restore #8508

Are you sure you want to change the base?

Introduce WG Checkpoint Restore #8508

Uh oh!

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!

k8s-ci-robot commented Jul 3, 2025

Uh oh!

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!

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!

Choose a reason for hiding this comment

Uh oh!

adrianreber commented Jul 20, 2025

Uh oh!

k8s-ci-robot commented Jul 20, 2025

Uh oh!

Uh oh!

rst0git Jul 19, 2025 •

edited

Loading