Exception request for KEP-5823 (Pod-Level Checkpoint/Restore)

[Radostin Stoyanov]

To sig-node, release-team, kubernetes-sig-release,

We would like to request an exception for the Pod-Level Checkpoint/Restore KEP. The KEP has been through multiple rounds of reviews, converging toward consensus, with a few minor comments remaining outstanding.

Many thanks,

Radostin

- Enhancement name: Pod-Level Checkpoint/Restore

- Enhancement status (alpha/beta/stable): alpha

- SIG: sig-node

- k/enhancements repo issue #: https://github.com/kubernetes/enhancements/issues/5823

- PR #’s: https://github.com/kubernetes/enhancements/pull/5851 ("KEP-5823: Pod-Level Checkpoint/Restore")

- Additional time needed (in calendar days, due end of day AoE): 2 days, end of day, 13 February 2026
- Reason this enhancement is critical for this milestone:

  - The Checkpoint Restore WG has been working on introducing a minimal set of CRI interfaces that would enable the development of the Pod Checkpoint/Restore functionality in runtimes such as CRI-O and containerd. Missing the release milestone would set back the integration of these interfaces across the stack, delay runtime implementations, and postpone the broader ecosystem validation and adoption.

- Risks from adding code late: (to k8s stability, testing, etc.)

  - The only risk is decreased development time.
- Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.)

  - Cutting the enhancement would delay the roadmap of the Checkpoint Restore WG, where multiple proposals depend on the behavior of the Pod-level Checkpoint/Restore CRI APIs, and reduce the overall effectiveness and progress of the WG.

[Radostin Stoyanov]

To sig-node, release-team, kubernetes-sig-release,

If possible, we would like to revise the additional time needed in the original request to 5 days.

Many thanks,

Radostin

[Ryota]

Hi all,

The release team is APPROVING this exception request for KEP-5823 based on the discussion in the Slack thread[0], given that active reviews are taking place.

Your updated deadline is the end of day Monday 16th February, 2026 (Anywhere-on-Earth) / 12:00 pm UTC Tuesday 17th February, 2026.

Thanks,
Ryota Sawada
v1.36 Release Team Lead

[0]: https://kubernetes.slack.com/archives/C2C40FMNF/p1770918538224839

[Ryota]

As discussed in the Slack thread[0], the PR did not make for the extended deadline of end of day Monday 16th February, 2026 (AoE), we will proceed with removing this KEP from the v1.36 milestone.

We look forward to seeing this KEP to land as a part of the next v1.37 or future release, where it can receive proper review and tracking in time.

Thanks for your understanding and contributions!

Thanks,
Ryota Sawada
v1.36 Release Team Lead

[0]: https://kubernetes.slack.com/archives/C2C40FMNF/p1770918538224839