From e385d552c59be2fdde040d679b5f4336587e6751 Mon Sep 17 00:00:00 2001 From: mazswojejzony Date: Sun, 5 Apr 2015 22:21:03 +0200 Subject: [PATCH 1/2] Fixed default config for kube-proxy on minions Without this fix kube-proxy on minions cannot connect to master as `MASTER_IP` is not reachable. --- cluster/ubuntu-cluster/configure.sh | 1 + 1 file changed, 1 insertion(+) diff --git a/cluster/ubuntu-cluster/configure.sh b/cluster/ubuntu-cluster/configure.sh index fcf52caf53..a87d47a73e 100755 --- a/cluster/ubuntu-cluster/configure.sh +++ b/cluster/ubuntu-cluster/configure.sh @@ -202,6 +202,7 @@ while true; do # set MINION IP in default_scripts/kubelet sed -i "s/MY_IP/${myIP}/g" default_scripts/kubelet sed -i "s/MASTER_IP/${masterIP}/g" default_scripts/kubelet + sed -i "s/MASTER_IP/${masterIP}/g" default_scripts/kube-proxy cpMinion break ;; From 0062da495693422c80d6b9ddab243142583dc360 Mon Sep 17 00:00:00 2001 From: mazswojejzony Date: Sun, 5 Apr 2015 22:38:24 +0200 Subject: [PATCH 2/2] Added extra info on 10.0.0.0/16 network Using 10.0.0.0/16 for flannel network and 10.10.103.x for example cluster network is a bit misleading as people may think they should use the same network for both flannel and eth0 interfaces. This commit tries to clarify that flannel shall use different network. --- docs/getting-started-guides/ubuntu_multinodes_cluster.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/getting-started-guides/ubuntu_multinodes_cluster.md b/docs/getting-started-guides/ubuntu_multinodes_cluster.md index b81cdba957..20d0429acb 100644 --- a/docs/getting-started-guides/ubuntu_multinodes_cluster.md +++ b/docs/getting-started-guides/ubuntu_multinodes_cluster.md @@ -114,8 +114,10 @@ If you want a node acts as **both running the master and minion**, please choose 2. On any node: `$ /opt/bin/etcdctl mk /coreos.com/network/config '{"Network":"10.0.0.0/16"}'` + + Note the `10.0.0.0/16` is a virtual network address. It has nothing to do with master and minions IP addresses assigned by the cloud provider. In other words even if your master and minions use address from another network (e.g. 172.16.0x) you can still use `10.0.0.0/16` for your virtual network. - > You can use the below command on another node to comfirm if the network setting is correct. + > You can use the below command on another node to confirm if the network setting is correct. > `$ /opt/bin/etcdctl get /coreos.com/network/config`