whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

change to relative path

Browse Source 
Co-authored-by: Qiming Teng <tengqm@outlook.com>
This commit is contained in:
Tom Kivlin
2022-05-24 07:40:26 +01:00
committed by GitHub
parent 4c1b181aff
commit f453118e4d
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins.md
+2 -1
View File
@@ -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. 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. 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 >}} {{< /note >}}
For specific information about how a Container Runtime manages the CNI plugins, see the documentation for that Container Runtime, for example: For specific information about how a Container Runtime manages the CNI plugins, see the documentation for that Container Runtime, for example: