CRI API reference at Container Runtime page is stale

[SergeyKanzhelev]

This is a Bug Report

/sig node
/kind bug
/priority important-soon
/help

Problem:
This page https://kubernetes.io/docs/setup/production-environment/container-runtimes/#cri-versions suggests that v1alpha2 is still supported. However it was not a case for a few versions now.

Also this page https://kubernetes.io/docs/concepts/architecture/cri/ links the quite old CRI API proto page. Simply pointing on master branch should be better unless we want to keep bumping the link for each release.

Proposed Solution:

Page to Update:

• https://kubernetes.io/docs/setup/production-environment/container-runtimes/#cri-versions
• https://kubernetes.io/docs/concepts/architecture/cri/

[k8s-ci-robot]

@SergeyKanzhelev:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

This is a Bug Report

/sig node
/kind bug
/priority important-soon
/help

Problem:

Proposed Solution:

Page to Update:
https://kubernetes.io/...

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.

[tengqm]

/triage accepted

[thisisharrsh]

I would like to work on this issue.

[thisisharrsh]

/assign

[thisisharrsh]

We need to correct both statements here, as they are misleading. They suggest that users can rely on v1alpha2, which is incorrect because v1alpha2 has been deprecated and should not be used as a fallback.

website/content/en/docs/setup/production-environment/container-runtimes.md

Lines 172 to 179 in 92fad83

	## CRI version support {#cri-versions}
	Your container runtime must support at least v1alpha2 of the container runtime interface.
	Kubernetes [starting v1.26](/blog/2022/11/18/upcoming-changes-in-kubernetes-1-26/#cri-api-removal)
	_only works_ with v1 of the CRI API. Earlier versions default
	to v1 version, however if a container runtime does not support the v1 API, the kubelet falls back to
	using the (deprecated) v1alpha2 API instead.

[sftim]

This is important, but:
/remove-priority important-soon
/priority important-longterm

The issues at https://github.com/kubernetes/website/issues?q=is%3Aissue+is%3Aopen+label%3Apriority%2Fimportant-soon are the ones we really want to focus on.

[SergeyKanzhelev]

sorry, didn't mean to hijack your prioritization. I was mostly thought from severity perspective as the info we give is incorrect for a few releases already.

[thisisharrsh]

The issue is fixed here: #48398