Add documentation for container checkpointing feature (KEP 2008)

[adrianreber]

Pull request for KEP 2008:

• Add Forensic Container Checkpointing KEP enhancements#1990
• Forensic Container Checkpointing enhancements#2008
• Minimal checkpointing support kubernetes#104907
• Add documentation for container checkpointing feature (KEP 2008) #31753 (previous PR for 1.24 (not merged))

CC: @sftim (you reviewed my previous 1.24 attempt of this documentation PR)

[netlify]

👷 Deploy Preview for kubernetes-io-vnext-staging processing.

Name	Link
🔨 Latest commit	df55ed5
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/62cee5afea519a0008f4a42e

[adrianreber]

CC: @mikebrow

[sftim]

Based on:

TODO: Add more information about return codes once CRI implementation have checkpoint/restore.

/retitle [WIP] Add documentation for container checkpointing feature (KEP 2008)

[adrianreber]

Based on:

TODO: Add more information about return codes once CRI implementation have checkpoint/restore.

/retitle [WIP] Add documentation for container checkpointing feature (KEP 2008)

We will not be able to fix this TODO before the release. Without the release the new CRI API is not available and cannot be implemented by the CRI implementation. This TODO can only be fixed after the release.

[chrisnegus]

This reads really well. I was hoping you could add a bit more in your return codes comment.

[jihoon-seo]

/remove-language ko zh

[reylejano]

@adrianreber , when this PR is ready for review, please remove [WIP] from the title
/milestone 1.25
/assign @sethmccombs
/cc @kcmartin

[reylejano]

I suggest removing this section and create a GitHub issue to track this

Suggested change

	{{< comment >}}
	TODO: Add more information about return codes once CRI implementation have checkpoint/restore.
	This TODO cannot be fixed before the release, because the CRI implementation need
	the Kubernetes changes to be merged to implement the new CheckpointContainer CRI API
	call. We need to wait after the 1.25 release to fix this.
	{{< /comment >}}

[reylejano]

Hi @adrianreber , the 1.25 Docs complete deadline passed.
Please address comments and feedback on this PR as soon as possible

[reylejano]

I can address my comment in a follow-up PR
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: reylejano

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:

• content/en/OWNERS [reylejano]

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

[krol3]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: a32cde75059bab4efaa4add4cd2d680f9d976f47

[adrianreber]

Sorry. I was away for some time and not able to react in a timely manner. I can do any fixup needed if you let me know what you would like to have changed.