<p>I have a Kubernetes-orchestraded infrastructure that is served on an AWS-hosted cluster. I'd like to have routines that would allow me to spawn similar infrastructures. The difference between the original infrastructure and the newly-spawned ones would mainly be the DNS's used and the images that I would serve.</p>

<p>My question is: What is the most appropriate place for this similar-infrastructure-spawning code to reside: Kubernetes ? My CI/CD tool, Drone? Some other DevOps stack component of which I'm not even aware?</p>

<p>Do you ever think about InfraAsCode tech.</p>

<p>You can directly develop your infrastructure using code like:</p>

<ul>
<li>Cloudformation (AWS)</li>
<li>Terraform (multi provider)</li>
<li>Ansible</li>
<li>...</li>
</ul>

<p>You will then be able to configure all providers services (not only your cluster)</p>

<p>You will then be able to deploy it with a single command and use parameters on it.</p>

<p>Otherwise you can also you a tool like Kops (<a href="https://github.com/kubernetes/kops" rel="nofollow noreferrer">https://github.com/kubernetes/kops</a>) to automate deployment of you K8s cluster.</p>

<p>Once you choose the right tool, you will then be able to source it using Git repository or whatever.</p>
