Clarity on scope of container runtime re. CNI
Co-authored-by: Mike Brown <brownwm@us.ibm.com>
This commit is contained in:
parent
f453118e4d
commit
c3629b395d
|
@ -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.
|
||||
|
|
Loading…
Reference in New Issue