Editing Kubernetes Controller (section)

== Install pod network ==

Pod networking is provided by an external plugin implementing the CNI specification; this section describes the deployment of the '''kube-router''' plugin.  Instructions on how to deploy the '''flannel''' plugin can be found [[Kubernetes Flannel Network Plugin|here]].

Full instructions on how to install and use this plugin can be found at https://github.com/cloudnativelabs/kube-router/blob/master/docs/kubeadm.md.  This plugin implements both the pod network and the proxy functions -- so the ''kube-proxy'' daemonset is no longer needed.  

Grab the manifest straight from their GitHub site:

 wget https://raw.githubusercontent.com/cloudnativelabs/kube-router/master/daemonset/kubeadm-kuberouter.yaml

Edit the manifest to remove the '--run-firewall=true' option, set the '--run-service-proxy' option to 'ture', and add another option that says:

 --kubeconfig=/var/lib/kube-router/kubeconfig/config

Then you will need to create that directory and populate it:

 sudo mkdir -p /var/lib/kube-router/kubeconfig
 sudo cp /etc/kubernetes/admin.conf /var/lib/kube-router/kubeconfig/config

Not sure yet if this needs to be done for all nodes, or just the master ...

This will implement all routing onto the network interface that supports the default route for the host systems.  If, however, there is a secondary network that is targeted for cluster communications, we need to do one more thing:  Change the default IP address for the node -- at least as far as the kubelet daemon is concerned.  The brute force way of doing this is to modify the '''/etc/sysconfig/kubelet''' file, adding one parameter to the end of the line:

 KUBELET_EXTRA_ARGS= ..... --node-ip=10.1.0.99

This should be done before the ''kubeadm init'' command above -- in which case the node's InternalIP address is already set.  If you do it after the ''kubeadm init'', then restart kubelet now and it will be happy, and (eventually) everything else will be happy too -- though some pods may need to be manually restarted (such as the kube-router pods that get started as soon as the node is joined to the network).  Ideally we need to find a way to set this during the kubeadm join process ... stay tuned ...