<p>I have application that have some user settings and it runs on kubernetes cluster.
I would like the user settings to survive application crash/pod restart.</p>
<p>I was thinking first about having a DB instance for keeping it outside of kubernetes. Then I thought, maybe I could just abuse etcd to store small amount of custom data.
Is it a good approach to keep things simple?</p>
<p>Another options I see:</p>
<ol>
<li>separate db instance outside of kubernetes(overkill)</li>
<li>some json file on PV volume in kubernetes being constantly re-read.</li>
<li>perhaps use hashicorp vault?</li>
</ol>
<p>What would you use? Its very small amount of data</p>

Wojtas.Zet
<p>If you want to use etcd, a Kubernetes built-in database, it's not really suited for this purpose and shouldn't be used in practice. App shouldn't know about Kubernetes. You need to use DB or PVC to store app related objects in a disk (for example json, yaml or other files).</p>
