<p>What is the best practice when one needs to have slightly different configs depending on whether it is being run locally or in the cloud?</p>

<p>For example say that locally (e.g. minikube) I need to create a secret and use it to authenticate.</p>

<p>But this authentication is not necessary when running in the cloud.</p>

<p>One obvious way to achieve this would be to have 2 different yaml files, but that really does not sound like a good idea. What is the best practice in such cases?</p>

Al Wld
<p>Explore <a href="https://kustomize.io" rel="nofollow noreferrer">Kustomize</a> which is a purely declarative approach and a template-free way to customize application configuration. You have a base config and then depending on environment you can create overlays to override the base config.</p>

<p><a href="https://github.com/kubernetes-sigs/kustomize/tree/master/examples/helloWorld" rel="nofollow noreferrer">https://github.com/kubernetes-sigs/kustomize/tree/master/examples/helloWorld</a></p>
