Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
K
k3s
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Jacklull
k3s
Commits
9fe0d744
Commit
9fe0d744
authored
Jul 06, 2015
by
Tim Hockin
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update networking doc wrt --configure-cbr0
parent
6c884018
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
14 deletions
+6
-14
networking.md
docs/networking.md
+6
-14
No files found.
docs/networking.md
View file @
9fe0d744
...
@@ -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
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment