whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add Calico, NetworkPolicy to the from-scratch networking section.

Browse Source
This commit is contained in:
Casey Davenport
2016-09-07 10:12:30 -07:00
parent e53cf66b4e
commit 2ee8a639fb
1 changed files with 20 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/getting-started-guides/scratch.md
+19 -4
View File
@@ -57,6 +57,7 @@ on how flags are set on various components.
### Network ### Network
#### Network Connectivity
Kubernetes has a distinctive [networking model](/docs/admin/networking). Kubernetes has a distinctive [networking model](/docs/admin/networking).
Kubernetes allocates an IP address to each pod. When creating a cluster, you Kubernetes allocates an IP address to each pod. When creating a cluster, you
@@ -66,21 +67,25 @@ the node is added. A process in one pod should be able to communicate with
another pod using the IP of the second pod. This connectivity can be another pod using the IP of the second pod. This connectivity can be
accomplished in two ways: accomplished in two ways:
- Configure network to route Pod IPs - **Configure underlay network to route Pod IPs**
- Harder to setup from scratch. - Harder to setup from scratch.
- Google Compute Engine ([GCE](/docs/getting-started-guides/gce)) and [AWS](/docs/getting-started-guides/aws) guides use this approach. - Google Compute Engine ([GCE](/docs/getting-started-guides/gce)) and [AWS](/docs/getting-started-guides/aws) guides use this approach.
- Need to make the Pod IPs routable by programming routers, switches, etc. - Need to make the Pod IPs routable by programming routers, switches, etc.
- Can be configured external to Kubernetes, or can implement in the "Routes" interface of a Cloud Provider module. - This can be done in a few different ways:
- Implement in the "Routes" interface of a Cloud Provider module.
- Manually configure static routing external to Kubernetes.
- Generally highest performance. - Generally highest performance.
- Create an Overlay network - **Use a network plugin**
- Easier to setup - Easier to setup
- Traffic is encapsulated, so per-pod IPs are routable. - Pod IPs are made accessible through route distribution or encapsulation.
- Examples: - Examples:
- [Flannel](https://github.com/coreos/flannel) - [Flannel](https://github.com/coreos/flannel)
- [Calico](http://https://github.com/projectcalico/calico-containers)
- [Weave](http://weave.works/) - [Weave](http://weave.works/)
- [Open vSwitch (OVS)](http://openvswitch.org/) - [Open vSwitch (OVS)](http://openvswitch.org/)
- Does not require "Routes" portion of Cloud Provider module. - Does not require "Routes" portion of Cloud Provider module.
- Reduced performance (exactly how much depends on your solution). - Reduced performance (exactly how much depends on your solution).
- More information on network plugins can be found [here](/docs/admin/networking#how-to-achieve-this).
You need to select an address range for the Pod IPs. You need to select an address range for the Pod IPs.
@@ -116,6 +121,16 @@ Also, you need to pick a static IP for master node.
- Open any firewalls to allow access to the apiserver ports 80 and/or 443. - Open any firewalls to allow access to the apiserver ports 80 and/or 443.
- Enable ipv4 forwarding sysctl, `net.ipv4.ip_forward = 1` - Enable ipv4 forwarding sysctl, `net.ipv4.ip_forward = 1`
#### Network Policy
Kubernetes enables the definition of fine-grained network policy between Pods
using the [NetworkPolicy](/docs/user-guide/networkpolicy) resource.
For clusters which choose to enable NetworkPolicy, the Calico
[policy controller addon](https://github.com/kubernetes/kubernetes/tree/master/cluster/addons/calico-policy-controller)
can enforce the NetworkPolicy API on top of native cloud-provider networking,
Flannel, or Calico networking.
### Cluster Naming ### Cluster Naming
You should pick a name for your cluster. Pick a short name for each cluster You should pick a name for your cluster. Pick a short name for each cluster