From 5246ba43a95e5cb84ee530ec31530209c05c3607 Mon Sep 17 00:00:00 2001 From: Ayushman Mishra Date: Fri, 15 Jul 2022 12:23:27 +0530 Subject: [PATCH] Remove list of container runtimes tested with v1.24 --- .../troubleshooting-cni-plugin-related-errors.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/troubleshooting-cni-plugin-related-errors.md b/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/troubleshooting-cni-plugin-related-errors.md index 91a471290d..34e2b112ef 100644 --- a/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/troubleshooting-cni-plugin-related-errors.md +++ b/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/troubleshooting-cni-plugin-related-errors.md @@ -13,11 +13,6 @@ To avoid CNI plugin-related errors, verify that you are using or upgrading to a container runtime that has been tested to work correctly with your version of Kubernetes. -For example, the following container runtimes are being prepared, or have already been prepared, for Kubernetes v1.24: - -* containerd v1.6.4 and later, v1.5.11 and later -* The CRI-O v1.24.0 and later - ## About the "Incompatible CNI versions" and "Failed to destroy network for sandbox" errors Service issues exist for pod CNI network setup and tear down in containerd