From c3629b395de5705b038af57f50616ae6c02bf96d Mon Sep 17 00:00:00 2001 From: Tom Kivlin <52716470+tomkivlin@users.noreply.github.com> Date: Tue, 24 May 2022 17:22:58 +0100 Subject: [PATCH] Clarity on scope of container runtime re. CNI Co-authored-by: Mike Brown --- .../extend-kubernetes/compute-storage-net/network-plugins.md | 2 +- 1 file changed, 1 insertion(+), 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 524d0d59cb..1ac4c79f8c 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 @@ -26,7 +26,7 @@ CNI specification (plugins can be compatible with multiple spec versions). ## Installation -The Container Runtime manages its own CNI plugins. +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.