<p>Through a stroke of luck I've been given an extremely powerful server in my office - I'd love to somehow set up a replica of our staging Kubernetes environment on it. Our staging Kube environment is 5 nodes running on AWS that each have different configurations. I can't find much in the way of best practice guides (probably because this is a very weird use case) for this configuration.</p>

<p>My gut feel is this:</p>

<ul>
<li>Install some kind of bare metal OS on the machine</li>
<li>Set up multiple VMs on the machine each configured to mirror a node from staging</li>
<li>Install the Kube master on one of the machines</li>
<li>Enrol each of the other VMs as a node under kubernetes</li>
<li>Run my deployments</li>
</ul>

<p>Is there any better way for me to configure this or any potential issues I may hit/roadblocks if I follow this approach?</p>

<p>If you want to have it everything in one machine, I would also go for the multi-vm option. With Vagrant you could try to make the process simpler. This could help you:</p>

<p><a href="https://github.com/pires/kubernetes-vagrant-coreos-cluster" rel="nofollow noreferrer">https://github.com/pires/kubernetes-vagrant-coreos-cluster</a></p>

<p>After setting up the cluster you could adapt it to mimic the state of your staging cluster. </p>

<p>The only issue that comes to mind is that of overlay networking an external access. If you configure NAT networking you would have issues with external access and probably no issue with the network overlay. On the other side, I am not 100% certain how the overlay network would work in a bridged setting. </p>
