2a8203559a
The 'kube-proxy --cleanup' checks that ip_vs.ko exists/is loaded. To do this it ends up looking in /lib/modules/... and generates an error: `Running modprobe ip_vs failed with message...`. Add -v /lib/modules:/lib/modules to instructions. Signed-off-by: Don Bowman <db@donbowman.ca>
1.6 KiB
Deploying kube-router with kubeadm
Please follow the steps to install Kubernetes cluster with Kubeadm, however must specify --pod-network-cidr when you run kubeadm init.
Kube-router relies on kube-controller-manager to allocate pod CIDR for the nodes.
Kube-router provides pod networking, network policy and high perfoming IPVS/LVS based service proxy. Depending on you choose to use kube-router for service proxy you have two options.
kube-router providing pod networking and network policy
For the step #3 Installing a pod network install a kube-router pod network and network policy add-on with the following command:
KUBECONFIG=/etc/kubernetes/admin.conf kubectl apply -f https://raw.githubusercontent.com/cloudnativelabs/kube-router/master/daemonset/kubeadm-kuberouter.yaml
kube-router providing service proxy, firewall and pod networking.
For the step #3 Installing a pod network install a kube-router pod network and network policy add-on with the following command:
KUBECONFIG=/etc/kubernetes/admin.conf kubectl apply -f https://raw.githubusercontent.com/cloudnativelabs/kube-router/master/daemonset/kubeadm-kuberouter-all-features.yaml
Now since kube-router provides service proxy as well. Run below commands to remove kube-proxy and cleanup any iptables configuration it may have done.
KUBECONFIG=/etc/kubernetes/admin.conf kubectl -n kube-system delete ds kube-proxy
docker run --privileged -v /lib/modules:/lib/modules --net=host k8s.gcr.io/kube-proxy-amd64:v1.10.2 kube-proxy --cleanup