KEP-2008: Graduate "Forensic Container Checkpointing" to GA

[adrianreber]

As defined in the existing KEP the steps to graduate from Beta to GA are

CRI-O as well as containerd have to have implemented the corresponding CRI APIs:

• CRI-O
• containerd

Ensure that e2e tests are working with

• CRI-O
• containerd

Both requirements are fulfilled. containerd supports the corresponding CRI APIs since 2.0 and CRI-O since 1.25.

Tests are also running according to
https://storage.googleapis.com/k8s-triage/index.html?test=checkpoint#a3361808c39a7eb28162

• One-line PR description: Graduate "Forensic Container Checkpointing" to GA

• Issue link: Forensic Container Checkpointing #2008

[k8s-ci-robot]

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.

[k8s-ci-robot]

[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 derekwaynecarr, jpbetz 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:

• keps/prod-readiness/OWNERS
• keps/sig-node/OWNERS

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

[kannon92]

/ok-to-test

[haircommander]

@SergeyKanzhelev @mikebrow @samuelkarp do you think containerd 2.0 is new enough to consider the checkpoint CRI API GA?

[mrunalp]

Let's add the changes discussed in sig-node weekly meeting to make this opt-in through config at GA. Thanks!
cc: @mikebrow @dchen1107

[kannon92]

cc @tallclair

kubernetes/kubernetes#130016

I guess making this opt in for GA would also help this CVE. As of now I read that the disablement of the checkpoint feature gate is the recommended approach to mitigate the CVE.

[tallclair]

I guess making this opt in for GA would also help this CVE. As of now I read that the disablement of the checkpoint feature gate is the recommended approach to mitigate the CVE.

The issue is already fixed in v1.33, so we don't need to worry about mitigation strategies for this specific issue going forward. There may still be general concerns with checkpoints filling up the disk though, so cluster provisioners may still want to disable it.