Commit 9fe0d744 authored by Tim Hockin's avatar Tim Hockin

Update networking doc wrt --configure-cbr0

parent 6c884018
...@@ -96,24 +96,16 @@ outbound internet access. A linux bridge (called `cbr0`) is configured to exist ...@@ -96,24 +96,16 @@ outbound internet access. A linux bridge (called `cbr0`) is configured to exist
on that subnet, and is passed to docker's `--bridge` flag. on that subnet, and is passed to docker's `--bridge` flag.
We start Docker with: We start Docker with:
``` ```
DOCKER_OPTS="--bridge cbr0 --iptables=false --ip-masq=false" DOCKER_OPTS="--bridge=cbr0 --iptables=false --ip-masq=false"
``` ```
We set up this bridge on each node with SaltStack, in This bridge is created by Kubelet (controlled by the `--configure-cbr0=true`
[container_bridge.py](../cluster/saltbase/salt/_states/container_bridge.py). flag) according to the `Node`'s `spec.podCIDR`.
```
cbr0:
container_bridge.ensure:
- cidr: {{ grains['cbr-cidr'] }}
- mtu: 1460
```
Docker will now allocate `Pod` IPs from the `cbr-cidr` block. Containers Docker will now allocate IPs from the `cbr-cidr` block. Containers can reach
can reach each other and `Nodes` over the `cbr0` bridge. Those IPs are all each other and `Nodes` over the `cbr0` bridge. Those IPs are all routable
routable within the GCE project network. within the GCE project network.
GCE itself does not know anything about these IPs, though, so it will not NAT GCE itself does not know anything about these IPs, though, so it will not NAT
them for outbound internet traffic. To achieve that we use an iptables rule to them for outbound internet traffic. To achieve that we use an iptables rule to
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment