<p>I have a newbie Kubernetes setup question that I can't find the answer to. Maybe community friends can help me.</p>

<p><strong>MY SETUP</strong>:</p>

<p>I have a personal <a href="https://jupyter.ai/RnDLab" rel="nofollow noreferrer">R&amp;D Lab</a> created using a robust PC running:</p>

<ul>
<li><code>Fedora-30</code> (the outer Host O/S)</li>
<li>Multiple <code>LXC</code> O/S containers (as Guests running <code>CentOS-8</code>)</li>
<li>And <code>Docker CE</code> nested and running within those <code>LXC</code> guest containers</li>
</ul>

<p>Using this setup, I'm able to mutate the "personality" of this environment to assume various technology and application development stacks.</p>

<p>Now the outer Host and LXC Guest O/S' all have static IP-address on the same subnet as any other device on my personal (home) network (basically <code>bridged</code> because it's just easier). The relevant hosts and IP-addresses for this question, are:</p>

<ul>
<li><code>Fedora-30</code> outer Host (the PC): <code>192.168.0.16/24</code></li>
<li><code>vps10 (CentOS-8)</code> LXC guest: <code>192.168.0.180/24</code> -- <code>k8s00</code></li>
<li><code>vps11 (CentOS-8)</code> LXC guest: <code>192.168.0.181/24</code> -- <code>k8s01</code></li>
<li><code>vps12 (CentOS-8)</code> LXC guest: <code>192.168.0.182/24</code> -- <code>k8s02</code></li>
<li><code>vps13 (CentOS-8)</code> LXC guest: <code>192.168.0.183/24</code> -- <code>k8s03</code></li>
</ul>

<p>I would like to setup a small Kubernetes cluster, with <code>k8s00</code> (above) being it's master node, and with <code>k8s01</code>, <code>k8s02</code> and <code>k8s03</code> (above) being the worker nodes. Again, these are LXC O/S containers with Docker CE nested within them (all working well).</p>

<p><strong>MY QUESTION</strong>:</p>

<p>As I set up Kubernetes, I would like to keep these IP-addresses  (since other R&amp;D Lab projects depend on them). Yet I can't tell from the documentation if I can or cannot keep them. In other words, does the below initialization command (example below) imply that I need to wipe out all IP-addresses and let it take over IP-address assignment; <strong>or</strong> I don't need to do that because the command simply creates an "overlay network" using the specified CIDR (atop my aforementioned static IP-addresses).</p>

<p><em>Many documents and books focus on super simple setups or all-in-a-box setups, which don't apply to my scenario here</em>.</p>

<p>Anyway, I hope it's the latter (i.e. being able to keep my IP-addresses) because they effectively represent the <code>bare-metal</code> addresses of those <code>LXC</code> "servers", which I would like to keep.</p>

<pre><code>vps10$ sudo kubeadm init --pod-network-cidr=Some-Network/Some-Mask [other_options]
</code></pre>

<p><strong>P.S.</strong> Assuming the answer is that I can keep my said static IP-addresses, what CIDR might be recommend for the above command? Same subnet; different subnet, etc.</p>

<p>Sorry for the verbose question. This will literally be my first Kubernetes setup, and things are already complicated, so I appreciate any walk-through answers.</p>

<p>Thanks. I hope this helps others, too.
<strong>\(◠﹏◠)/</strong></p>

<p>You can keep your k8s cluster nodes static ip addresses.  <br>
While kubeadm init, your specified pod network subnet should not overlap with your cluster nodes subnet. In below command, specified pod subnet is not overlapping with your cluster subnet.</p>

<pre><code>sudo kubeadm init --pod-network-cidr=10.16.96.0/24 --apiserver-advertise-address=&lt;master-node-ip_addr&gt; 
</code></pre>

<p>You can initialize pod subnet of your choice but if it will overlap with you cluster nodes subnet, then it will create a complicated situation. (as these are 2 different subnetworks but if you specify same subnet range then your newly created pod could have a ip address same as one of your cluster node ip address)</p>
