From a6f31d4896f33c69f84f24e51ef7515d8ab67527 Mon Sep 17 00:00:00 2001 From: Kevin Kirsche Date: Fri, 2 Jun 2017 06:21:21 -0400 Subject: [PATCH] Clarify CNI acronym Fixes kubernetes/kubernetes.github.io#3964 --- docs/setup/independent/create-cluster-kubeadm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/setup/independent/create-cluster-kubeadm.md b/docs/setup/independent/create-cluster-kubeadm.md index 63380682f4..dbe7346598 100644 --- a/docs/setup/independent/create-cluster-kubeadm.md +++ b/docs/setup/independent/create-cluster-kubeadm.md @@ -221,7 +221,7 @@ each other. **The network must be deployed before any applications. Also, kube-dns, a helper service, will not start up before a network is installed. kubeadm only -supports CNI based networks (and does not support kubenet).** +supports Container Network Interface (CNI) based networks (and does not support kubenet).** Several projects provide Kubernetes pod networks using CNI, some of which also support [Network Policy](/docs/concepts/services-networking/networkpolicies/). See the [add-ons