<p>since this morning i've a question in my mind. 
What is the best things to manage file configuration on kubernetes!</p>

<p>For the moment we use <code>PVC &amp; PV</code> </p>

<p>But i would want to update <strong>automatically</strong> during the <strong>CI pipeline</strong> the config files . For one application we have almost <strong>10 configs files</strong> </p>

<p>How can i update it automatically with kubernetes ? 
Or do you think i will have to change for configMap ?</p>

<p>I still reading the documentation on internet but i dont find an answear to my question :( </p>

<p>Thanks </p>

<p>If it is configuration then a ConfigMap fits. You can update the ConfigMap resource descriptor file as part of your CI pipeline and then apply that change with 'kubectl apply' and you can do a rolling update on your app. This moves you in the direction of every config change being a tracked and versioned change. </p>

<p>You may also want to look at Secrets, depending on how sensitive your config is. </p>

<p>I guess you will have the same number of files whether in a PV or a ConfigMap - the choice only affects how they are made available to the app in Kubernetes. But if you find your CI pipelines are doing a lot of replacements then a templating system could help. I'd suggest looking at helm so that you can pass parameters into your deployments at the time of deploy. </p>
