From eda01ffa89981662e5a9b9a3e6c37b69791177fe Mon Sep 17 00:00:00 2001
From: Michael <cloudyonspring@126.com>
Date: Mon, 18 Jul 2022 22:32:31 +0800
Subject: [PATCH] [zh-cn] resync /troubleshooting-cni-plugin-related-errors.md

---
 .../troubleshooting-cni-plugin-related-errors.md     | 12 ------------
 1 file changed, 12 deletions(-)

diff --git a/content/zh-cn/docs/tasks/administer-cluster/migrating-from-dockershim/troubleshooting-cni-plugin-related-errors.md b/content/zh-cn/docs/tasks/administer-cluster/migrating-from-dockershim/troubleshooting-cni-plugin-related-errors.md
index e60db86be8..d7b6e3174d 100644
--- a/content/zh-cn/docs/tasks/administer-cluster/migrating-from-dockershim/troubleshooting-cni-plugin-related-errors.md
+++ b/content/zh-cn/docs/tasks/administer-cluster/migrating-from-dockershim/troubleshooting-cni-plugin-related-errors.md
@@ -23,18 +23,6 @@ Kubernetes.
 为了避免 CNI 插件相关的错误，需要验证你正在使用或升级到一个经过测试的容器运行时，
 该容器运行时能够在你的 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
--->
-
-例如，针对 Kubernetes v1.24 而言，以下容器运行时正在准备或已经就绪：
-
-* containerd v1.6.4 及更新版本、v1.5.11 及更新版本
-* CRI-O v1.24.0 及更新版本
-
 <!--
 ## About the "Incompatible CNI versions" and "Failed to destroy network for sandbox" errors
 -->