From f453118e4d2c573a6d0913acc8bf8a936c11cd67 Mon Sep 17 00:00:00 2001 From: Tom Kivlin <52716470+tomkivlin@users.noreply.github.com> Date: Tue, 24 May 2022 07:40:26 +0100 Subject: [PATCH] change to relative path Co-authored-by: Qiming Teng --- .../extend-kubernetes/compute-storage-net/network-plugins.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/en/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins.md b/content/en/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins.md index ae4b7f550c..524d0d59cb 100644 --- a/content/en/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins.md +++ b/content/en/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins.md @@ -32,7 +32,8 @@ The Container Runtime manages its own CNI plugins. Prior to Kubernetes 1.24, the CNI plugin was managed by the Kubelet using the `cni-bin-dir` and `network-plugin` command line parameters. These were both removed in Kubernetes 1.24, with management of the CNI no longer in scope of the Kubelet. -See [Troubleshooting CNI plugin-related errors](https://kubernetes.io/docs/tasks/administer-cluster/migrating-from-dockershim/troubleshooting-cni-plugin-related-errors/) if you are facing issues following the removal of dockershim. +See [Troubleshooting CNI plugin-related errors](/docs/tasks/administer-cluster/migrating-from-dockershim/troubleshooting-cni-plugin-related-errors/) +if you are facing issues following the removal of dockershim. {{< /note >}} For specific information about how a Container Runtime manages the CNI plugins, see the documentation for that Container Runtime, for example: