<p>I have a CentOS lab environment that holds 3 systems (A, B, C).  Each system has 4 network links:</p>

<ul>
<li>eth0 is 1g and my public management interface (VLAN10)</li>
<li>eth1 is 10g my iscsi interface (VLAN172)</li>
<li>eth2 is 10g available for kubernetes (VLAN192: 192.168.1.x)</li>
<li>eth3 is 10g available for kubernetes (VLAN192: 192.168.2.x)</li>
</ul>

<p>eth2 and eth3 are not bonded or in any sort of config where they are aware of each other.  They are both in the same vlan and you can ping from eth2 to eth3 from any given system.</p>

<p>I'd like to setup Kubernetes to use eth2 and eth3 for all its work.  In particular, I want to keep traffic off the slower 1g network and off of the interface I'm using for iscsi.  All the kubernetes bits (control plane, data plane, applications, etc) to run over eth2 and eth3.</p>

<p>I may down the road want to open a specific service on eth0 for consumption (prometheus metrics).</p>

<p>Specific Config:</p>

<p>System A:</p>

<ul>
<li>eth0 is my public management interface (VLAN10: 10.10.10.1)</li>
<li>eth1 is my iscsi interface (VLAN172: 172.16.0.1)</li>
<li>eth2 is available for kubernetes (VLAN192: 192.168.1.1)</li>
<li>eth3 is available for kubernetes (VLAN192: 192.168.2.1)</li>
</ul>

<p>System B:</p>

<ul>
<li>eth0 is my public management interface (VLAN10: 10.10.10.2)</li>
<li>eth1 is my iscsi interface (VLAN172: 172.16.0.2)</li>
<li>eth2 is available for kubernetes (VLAN192: 192.168.1.2)</li>
<li>eth3 is available for kubernetes (VLAN192: 192.168.2.2)</li>
</ul>

<p>System C:</p>

<ul>
<li>eth0 is my public management interface (VLAN10: 10.10.10.3)</li>
<li>eth1 is my iscsi interface (VLAN172: 172.16.0.3)</li>
<li>eth2 is available for kubernetes (VLAN192: 192.168.1.3)</li>
<li>eth3 is available for kubernetes (VLAN192: 192.168.2.3)</li>
</ul>

<p>The default setup with <code>kubeadm init</code> seems to use all interfaces.</p>

<p>I can't seem to find any documentation to guide me....</p>

jcpunk
<p>As mentioned in the docs here <a href="https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/" rel="nofollow noreferrer">https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/</a></p>

<p>use the flag <code>--apiserver-advertise-address</code></p>

<p>ie <code>kubeadm init --apiserver-advertise-address 192.168.1.1</code></p>
