From d234d86af6fe163545dafb4de3842822b5a385d3 Mon Sep 17 00:00:00 2001 From: Trevor Pounds Date: Thu, 8 Oct 2015 23:04:16 -0700 Subject: [PATCH] Minor formatting cleanup. --- docs/getting-started-guides/scratch.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/getting-started-guides/scratch.md b/docs/getting-started-guides/scratch.md index b5e8d8ff83c..29bdc6dd185 100644 --- a/docs/getting-started-guides/scratch.md +++ b/docs/getting-started-guides/scratch.md @@ -472,13 +472,13 @@ because of how this is used later. - Alternate, manual approach: 1. Set `--configure-cbr0=false` on kubelet and restart. 1. Create a bridge - - e.g. `brctl addbr cbr0`. - 1. Set appropriate MTU - - `ip link set dev cbr0 mtu 1460` (NOTE: the actual value of MTU will depend on your network environment) - 1. Add the clusters network to the bridge (docker will go on other side of bridge). - - e.g. `ip addr add $NODE_X_BRIDGE_ADDR dev cbr0` + - `brctl addbr cbr0`. + 1. Set appropriate MTU. NOTE: the actual value of MTU will depend on your network environment + - `ip link set dev cbr0 mtu 1460` + 1. Add the node's network to the bridge (docker will go on other side of bridge). + - `ip addr add $NODE_X_BRIDGE_ADDR dev cbr0` 1. Turn it on - - e.g. `ip link set dev cbr0 up` + - `ip link set dev cbr0 up` If you have turned off Docker's IP masquerading to allow pods to talk to each other, then you may need to do masquerading just for destination IPs outside