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

Correction of what Kubelet did/could do in versions <1.24.

Browse Source 
Co-authored-by: Mike Brown <brownwm@us.ibm.com>
This commit is contained in:
Tom Kivlin
2022-05-24 17:23:40 +01:00
committed by GitHub
parent c3629b395d
commit 4ba0e82bd0
1 changed files with 1 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
+1 -1
View File
@@ -29,7 +29,7 @@ CNI specification (plugins can be compatible with multiple spec versions).
A Container Runtime, in the networking context, is a daemon on a node configured to provide CRI Services for kubelet. In particular the Container Runtime must be configured to load the CNI plugins required to implement the Kubernetes network model.
{{< note >}}
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 plugins could also be 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](/docs/tasks/administer-cluster/migrating-from-dockershim/troubleshooting-cni-plugin-related-errors/)