From b841cbaa1fc70d81a3b3617f5b0b2ba4b23de25b Mon Sep 17 00:00:00 2001 From: Mickey Boxell Date: Sat, 30 Apr 2022 16:21:57 -0700 Subject: [PATCH] Update content/en/blog/_posts/2022-05-03-kubernetes-release-1.24.md Co-authored-by: James Laverack --- content/en/blog/_posts/2022-05-03-kubernetes-release-1.24.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/blog/_posts/2022-05-03-kubernetes-release-1.24.md b/content/en/blog/_posts/2022-05-03-kubernetes-release-1.24.md index 99f2845c56..01a99c08dc 100644 --- a/content/en/blog/_posts/2022-05-03-kubernetes-release-1.24.md +++ b/content/en/blog/_posts/2022-05-03-kubernetes-release-1.24.md @@ -113,10 +113,10 @@ For example, the following container runtimes are being prepared, or have alread * CRI-O 1.24 and later Service issues exist for pod CNI network setup and tear down in containerd -v1.6.0-v1.6.3 when the CNI plugins have not been upgraded and/or the CNI config +v1.6.0–v1.6.3 when the CNI plugins have not been upgraded and/or the CNI config version is not declared in the CNI config files. The containerd team reports, "these issues are resolved in containerd v1.6.4." -With containerd v1.6.0-v1.6.3, if you do not upgrade the CNI plugins and/or +With containerd v1.6.0–v1.6.3, if you do not upgrade the CNI plugins and/or declare the CNI config version, you might encounter the following "Incompatible CNI versions" or "Failed to destroy network for sandbox" error conditions.