<p>I have a container type that I will need to intermittently add and delete from my cluster, but each different container instance will need a unique configuration in the form of environment variables.</p>
<p>What is the best way to structure this with Kubernetes? Should I have a separate workload for each container? Should I have one common workload and update the pod with new containers as needed?</p>
<p>The containers are isolated applications that don't have anything to do with their siblings.</p>

Josh
<p>I do it by</p>
<ul>
<li>Having a common deployment yaml. You should mount configmaps as environment variables</li>
<li>Packaging with Helm</li>
<li>Deploying with different values.yaml for each instance.</li>
</ul>
<p>As Harsh stated, you can also use Jobs pattern but I prefer having single file &amp; many values files instead of different jobs definitions.. Because if a key changes, you will need to update all job definitions..</p>
