kubeadm: add CRI timeout(s)

[saschagrunert]

Right now the timeout is hardcoded and inherited from previous critcl times:

https://github.com/kubernetes/kubernetes/blob/026c55e40de835464e769bad65c8a19940b61459/cmd/kubeadm/app/util/runtime/runtime.go#L63-L64

The pull timeout is set to unlimited, which is also the default for critcl:

https://github.com/kubernetes/kubernetes/blob/026c55e40de835464e769bad65c8a19940b61459/cmd/kubeadm/app/util/runtime/runtime.go#L174

Would it make sense to add a generic and pull timeout option to the kubeadm configuration without having a need for a KEP, @kubernetes/kubeadm-maintainers?

[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.

[neolit123]

/transfer kubeadm

[neolit123]

the v1beta4 config is locked and we don't have an ETA for vNext.
we don't do like k8s APIs and add fields to released APIs, i.e. ours are set in stone.

such a change missed the timing of v1beta4 which was released with 1.31, next to your addition of using the CRI lib.

best we can do as a quick fix is change the hardcoded timeout.

[saschagrunert]

@neolit123 then let's close this issue, I think having the crictl timeouts inherited is fine (expected behavior).