Commit 62f399fb authored by Rohit Jnagal's avatar Rohit Jnagal

Merge pull request #6453 from mazswojejzony/master

Ubuntu-cluster updates: configure.sh fix and guide update
parents 9e61d743 0062da49
...@@ -202,6 +202,7 @@ while true; do ...@@ -202,6 +202,7 @@ while true; do
# set MINION IP in default_scripts/kubelet # set MINION IP in default_scripts/kubelet
sed -i "s/MY_IP/${myIP}/g" 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/kubelet
sed -i "s/MASTER_IP/${masterIP}/g" default_scripts/kube-proxy
cpMinion cpMinion
break break
;; ;;
......
...@@ -114,8 +114,10 @@ If you want a node acts as **both running the master and minion**, please choose ...@@ -114,8 +114,10 @@ If you want a node acts as **both running the master and minion**, please choose
2. On any node: 2. On any node:
`$ /opt/bin/etcdctl mk /coreos.com/network/config '{"Network":"10.0.0.0/16"}'` `$ /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` > `$ /opt/bin/etcdctl get /coreos.com/network/config`
......
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