From 5686df80d5a3d1d7fdfec66fc27c80b89ba2efc2 Mon Sep 17 00:00:00 2001 From: Mickey Boxell Date: Sat, 30 Apr 2022 13:24:30 -0700 Subject: [PATCH] Update 2022-05-03-kubernetes-release-1.24.md Modifying CNI issue write up. --- .../blog/_posts/2022-05-03-kubernetes-release-1.24.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 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 1f63ff79a7..92c3eb24cf 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 @@ -108,9 +108,13 @@ For example, the following container runtimes are being prepared, or have alread * containerd v1.6.4 and later, v1.5.11 and later * 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 in cases where the -CNI plugins have not been upgraded and/or the CNI config version is not declared in the CNI config files. -These issues are resolved in containerd v1.6.4. +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 +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 +declare the CNI config version, you might encounter the following "Incompatible +CNI versions" or "Failed to destroy network for sandbox" error conditions. ## Other Updates