kubernetes
/
kops
mirror of https://github.com/kubernetes/kops.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add documentaion to kube-router section of docs/networking

This commit is contained in:
Murali Reddy 2017-08-24 10:35:07 +05:30
parent 34473e8602
commit af8d0f6917
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/networking.md
View File

@ -34,7 +34,7 @@ Several different providers are currently built into kops:
* [Canal (Flannel + Calico)](https://github.com/projectcalico/canal)
* [flannel](https://github.com/coreos/flannel)
* [kopeio-vxlan](https://github.com/kopeio/networking)
* [kube-router](https://github.com/cloudnativelabs/kube-router)
* [kube-router](./networking.md#kube-router-example-for-cni-ipvs-based-service-proxy-and-network-policy-enforcer)
* [weave](https://github.com/weaveworks/weave-kube)
The manifests for the providers are included with kops, and you simply use `--networking provider-name`.
@ -256,6 +256,8 @@ $ kops create cluster \
Currently kube-router supports 1.6 and above. Please note that kube-router will also provide service proxy, so kube-proxy will not be deployed in to the cluster.
No additional configurations are required to be done by user. Kube-router automatically disables source-destination check on all AWS EC2 instances. For the traffic within a subnet there is no overlay or tunneling used. For cross-subnet pod traffic ip-ip tunneling is used implicitly and no configuration is required.
### Validating CNI Installation
You will notice that `kube-dns` fails to start properly until you deploy your CNI provider.