From 25c4d396eae99e23c4ebe7155fde7700dd1130b9 Mon Sep 17 00:00:00 2001 From: Scott Keeler Date: Mon, 1 Oct 2018 14:50:57 -0400 Subject: docs: add contiv vpp Change-Id: I92227fc4968fc6a478beb7f38707b91e9f0635ec Signed-off-by: Scott Keeler --- docs/usecases/contiv/CUSTOM_MGMT_NETWORK.md | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 docs/usecases/contiv/CUSTOM_MGMT_NETWORK.md (limited to 'docs/usecases/contiv/CUSTOM_MGMT_NETWORK.md') diff --git a/docs/usecases/contiv/CUSTOM_MGMT_NETWORK.md b/docs/usecases/contiv/CUSTOM_MGMT_NETWORK.md new file mode 100644 index 00000000000..bf2937f2016 --- /dev/null +++ b/docs/usecases/contiv/CUSTOM_MGMT_NETWORK.md @@ -0,0 +1,26 @@ +### Setting Up a Custom Management Network on Multi-Homed Nodes + +If the interface you use for Kubernetes management traffic (for example, the +IP address used for `kubeadm join`) is not the one that contains the default +route out of the host, then you need to specify the management node IP address in +the Kubelet config file. Add the following line to: +(`/etc/systemd/system/kubelet.service.d/10-kubeadm.conf`): +``` +Environment="KUBELET_EXTRA_ARGS=--fail-swap-on=false --node-ip=" +``` +#### Example +Consider a 2 node deployment where each node is connected to 2 networks - +`10.0.2.0/24` and `192.168.56.0/24`, and the default route on each node points +to the interface connected to the `10.0.2.0/24` subnet. We want to use subnet +`192.168.56.0/24` for Kubernetes management traffic. Assume the addresses of +nodes connected to `192.168.56.0/24` are `192.168.56.105` and `192.168.56.106`. + +On the `192.168.56.105` node you add the following line to `10-kubeadm.conf`: +``` +Environment="KUBELET_EXTRA_ARGS=--fail-swap-on=false --node-ip=192.168.56.105" +``` +On the `192.168.56.106` node you add the following line to `10-kubeadm.conf`: +``` +Environment="KUBELET_EXTRA_ARGS=--fail-swap-on=false --node-ip=192.168.56.106" +``` + -- cgit 1.2.3-korg