Forensic Container Checkpointing

[adrianreber]

Enhancement Description

• One-line enhancement description (can be used as a release note): Forensic Container Checkpointing
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2008-forensic-container-checkpointing
• Discussion Link:
  • SIG Node weekly meeting: https://docs.google.com/document/d/1Ne57gvidMEWXR70OxxnRkYquAoMpt56o75oZtg-OeBg/edit
  • SIG Node planning doc for v1.23: https://docs.google.com/document/d/1U10J0WwgWXkdYrqWGGvO8iH2HKeerQAlygnqgDgWv4E/edit
• Primary contact (assignee): @adrianreber
• Responsible SIGs: Sig Node
• Enhancement target (which target equals to which milestone): No target so far
  • Alpha release target (x.y): 1.25
  • Beta release target (x.y): 1.30
  • Stable release target (x.y): 1.32
• Documentation
  • https://kubernetes.io/docs/reference/node/kubelet-checkpoint-api/
  • https://kubernetes.io/blog/2022/12/05/forensic-container-checkpointing-alpha/
  • https://kubernetes.io/blog/2023/03/10/forensic-container-analysis/

• Alpha (1.25)
  • KEP (k/enhancements) update PR(s):
    • Add Forensic Container Checkpointing KEP #1990
    • KEP-2008: changed to target 1.25 #3264
    • KEP 2008: update test plan #3406
  • Code (k/k) update PR(s):
    • Minimal checkpointing support kubernetes#104907
    • Extend checkpoint e2e test to check for results kubernetes#115155
  • Docs (k/website) update(s):
    • Add documentation for container checkpointing feature (KEP 2008) website#34940
    • Add blog post about forensic container checkpointing website#37412
    • Add blog post about forensic container analysis website#39759
    • Add link to checkpointing follow-up article website#39842
• Beta (1.30)
  • KEP (k/enhancements) update PR(s):
    • KEP-2008: Graduate "Forensic Container Checkpointing" to Beta #4288
  • Code (k/k) update PR(s):
    • Switch 'ContainerCheckpoint' from Alpha to Beta kubernetes#123215
  • Docs (k/website) update(s):
  • KEP-2008: Provide details about additional checkpoint/restore use cases #4305
  • Add 'checkpoint' command to kubectl kubernetes#120898
  • Abandoned PR: Add MaxCheckpointsPerContainer to the kubelet kubernetes#115888
• GA
  • KEP (k/enhancements) update PR(s):
    • KEP-2008: Graduate "Forensic Container Checkpointing" to GA #5090
  • Code (k/k) update PR(s):
  • Docs (k/website) update(s):

[adrianreber]

/sig node

[kikisdeliveryservice]

Discussion Link: N/A (or... at multiple conferences during the last years when presenting CRIU and container migration, there was always the question when will we see container migration in Kubernetes)

Responsible SIGs: maybe node

We recommend actively socializing your KEP with the appropriate sig to gain visibility, consensus and also for scheduling. Also as you are not sure of what SIG will sponsor this, reaching out to the SIGs to get clarity on that will be helpful to move your KEP forward.

[kikisdeliveryservice]

Hi @adrianreber

Any updates on whether this will be included in 1.20?

Enhancements Freeze is October 6th and by that time we require:

The KEP must be merged in an implementable state
The KEP must have test plans
The KEP must have graduation criteria
The KEP must have an issue in the milestone

Best,
Kirsten

[adrianreber]

Hello @kikisdeliveryservice

Any updates on whether this will be included in 1.20?

Sorry, but how would I decide this? There has not been a lot of feedback on the corresponding KEP which makes it really difficult for me to answer that question. On the other hand, maybe the missing feedback is a good sign that it will take some more time. So probably this will not be included in 1.20.

[kikisdeliveryservice]

Normally the sig would give a clear signal that it would be included. That would be by : reviewing the KEP, agreeing to the milestone proposals in the KEP etc.. I'd encourage you to keep in touch with them and start the 1.21 conversation early if this does not end up getting reviewed/merged properly by October 6th.

Best,
Kirsten

[adrianreber]

@kikisdeliveryservice Thanks for the guidance. Will do.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten