From fe21dfa5b307c9e3fd0424ae5c57eaeedf5cf71d Mon Sep 17 00:00:00 2001 From: Lee Calcote Date: Mon, 13 Jun 2016 08:33:31 -0500 Subject: [PATCH] Updated CNI spec reference CNI spec has moved from appc organization in github to containernetworking organization. --- docs/admin/network-plugins.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/admin/network-plugins.md b/docs/admin/network-plugins.md index 2b1adca8ec..f5e2d27192 100644 --- a/docs/admin/network-plugins.md +++ b/docs/admin/network-plugins.md @@ -31,7 +31,7 @@ Place plugins in `network-plugin-dir/plugin-name/plugin-name`, i.e if you have a ### CNI -The CNI plugin is selected by passing Kubelet the `--network-plugin=cni` command-line option. Kubelet reads the first CNI configuration file from `--network-plugin-dir` and uses the CNI configuration from that file to set up each pod's network. The CNI configuration file must match the [CNI specification](https://github.com/appc/cni/blob/master/SPEC.md), and any required CNI plugins referenced by the configuration must be present in `/opt/cni/bin`. +The CNI plugin is selected by passing Kubelet the `--network-plugin=cni` command-line option. Kubelet reads the first CNI configuration file from `--network-plugin-dir` and uses the CNI configuration from that file to set up each pod's network. The CNI configuration file must match the [CNI specification](https://github.com/containernetworking/cni/blob/master/SPEC.md), and any required CNI plugins referenced by the configuration must be present in `/opt/cni/bin`. ### kubenet