Remove vendor reference, typo...

This commit is contained in:
Chris Marino
2016-10-25 14:55:55 -07:00
parent f5ab3e9d33
commit 6a290cd6e7
2 changed files with 4 additions and 4 deletions
+3 -3
View File
@@ -162,10 +162,10 @@ You must install a pod network add-on so that your pods can communicate with eac
Several projects are available that enable Kubernetes pod networks. Some may also support [Network Policy](/docs/user-guide/networkpolicies/). See the [add-ons page](/docs/admin/addons/) for a complete list of available network add-ons.
By way of example, you can install [Weave Net](https://github.com/weaveworks/weave-kube) by logging in to the master and running:
You can install a pod network add-on with the following command:
# kubectl apply -f https://git.io/weave-kube
daemonset "weave-net" created
# kubectl apply -f <add-on_spec.yaml>
daemonset "<add-on_name>" created
If you prefer one of the other network providers please refer to their respective installation guides. You should only install one pod network per cluster.
@@ -6,7 +6,7 @@ assignees:
Kubernetes can be used to declare network policies which govern how Pods can communicate with each other. This document helps you get started using the Kubernetes [NetworkPolicy API](/docs/user-guide/networkpolicies), and provides a demonstration thereof.
In this article, we assume a network provider that supports the NetworkPolicy API has been installed. Network providers can be installed as add-ons using [kubeadmin](/docs/getting-started-guides/kubeadm/), or any other suitable cluster installer.
In this article, we assume a network provider that supports the NetworkPolicy API has been installed. Network providers can be installed as add-ons using [kubeadm](/docs/getting-started-guides/kubeadm/), or any other suitable cluster installer.
There are a number of network providers which support NetworkPolicy including: