Switch to CRI v1 API

[saschagrunert]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Using the CRI v1 API as new default.

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

None

Does this PR introduce a user-facing change?

Switching to CRI v1 API, which requires running at least Kubernetes v1.23.0 configured with a v1 runtime

[saschagrunert]

@feiskyer @mrunalp PTAL

[feiskyer]

Rebase the PR again?

[saschagrunert]

Rebase the PR again?

Done :)

[feiskyer]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: feiskyer, saschagrunert

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:

• OWNERS [feiskyer,saschagrunert]

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

[SergeyKanzhelev]

this PR makes the cri tools incompatible with the Containerd 1.5. Which is not ideal. As a minimum this needs to be communicated in readme and release notes. This may break users so implementing the fallback logic would be the best.

[Random-Liu]

this PR makes the cri tools incompatible with the Containerd 1.5. Which is not ideal. As a minimum this needs to be communicated in readme and release notes.

cri-tools is versioned with kubernetes version, and should support the same set of CRI versions with Kubernetes. @SergeyKanzhelev told me that we have conversion logic in Kubernetes to fallback to v1alpha2, can we reuse that in cri-tools?

[SergeyKanzhelev]

Created tracking task: #883

Since it is in master targeting 1.24 there is still some time to implement it.