Can Checkpoint endpoint support extra parameters to be passed to the CRI implementation ?

[yangchi]

At least from the current doc https://kubernetes.io/docs/reference/node/kubelet-checkpoint-api/ it seems only some very generic params like namespace and pod are allowed. I think this greatly limits this feature. For example, if CRIU is used as the underlying implementation for checkpoint, flags like "--tcp-close" and "tcp-established" are quite important for user to pass to it. It doesn't seem like there is a way to achieve it today. Can this be supported? Thank you!

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[yangchi]

/sig api-machinery

[pacoxu]

This was mentioned in https://github.com/kubernetes/enhancements/pull/5092/files#diff-be0828870a80495594eee46334524baae1420225887f55cc3099bf7d660101e6R382. Refer to kubernetes/enhancements#5091 for more. BTW, kubernetes/community#8508 may be a nice place for this discussion.

[yangchi]

@pacoxu thank you! Those are useful context. I will take a look.

[rst0git]

@yangchi You can set tcp-close or tcp-established with a CRIU configuration file (/etc/criu/runc.conf). The following page provides more information: https://criu.org/Configuration_files

This is currently a manual step and it can be improved. We are in the process of setting up a checkpoint/restore working group to address similar issues: kubernetes/community#8508

[yangchi]

Good to know. I will follow along that community thread. Thank you! I will close this one