<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>annexrichmond</author><text>yeah but if your org has orchestration tooling built around k8s, in a way it becomes much easier to provision a DB with k8s, setup the service, routing, networking, roles, etc than it would be in terraform.  especially if you have to repeat this process in like 20 envs (stage, prod) x multiple regions</text><parent_chain><item><author>_skel</author><text>I don&amp;#x27;t think the upsides are worth all the work.&lt;p&gt;You can spend a lot of time getting databases and other stateful workloads to work -- mess around with StatefulSet and PVC on top of all the normal Kubernetes concepts, and what do you get in the end? Are you really better off than you would have been if you ran the database in EC2?&lt;p&gt;Plus, &amp;quot;herds not pets&amp;quot; kind of breaks down once you start using StatefulSets and PVCs. Those things exist to make Kubernetes more like a static environment for workloads that can&amp;#x27;t handle being run like ephemeral cattle. So why not just keep using your static environment?&lt;p&gt;If Kubernetes is the only workload management control plane you have, then I guess this makes sense. But if you are already able to deploy your databases with existing tools, and those existing tools don&amp;#x27;t &lt;i&gt;really&lt;/i&gt; suck, it&amp;#x27;s probably not worth migrating. It would take a lot of time and introduce significant new risks and operational complexity without a compensating payoff.</text></item></parent_chain></comment><story><title>Running Databases on Kubernetes</title><url>https://questdb.io/blog/databases-on-k8s/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>superyesh</author><text>+1 Sometimes just because you can does not mean you should.</text><parent_chain><item><author>_skel</author><text>I don&amp;#x27;t think the upsides are worth all the work.&lt;p&gt;You can spend a lot of time getting databases and other stateful workloads to work -- mess around with StatefulSet and PVC on top of all the normal Kubernetes concepts, and what do you get in the end? Are you really better off than you would have been if you ran the database in EC2?&lt;p&gt;Plus, &amp;quot;herds not pets&amp;quot; kind of breaks down once you start using StatefulSets and PVCs. Those things exist to make Kubernetes more like a static environment for workloads that can&amp;#x27;t handle being run like ephemeral cattle. So why not just keep using your static environment?&lt;p&gt;If Kubernetes is the only workload management control plane you have, then I guess this makes sense. But if you are already able to deploy your databases with existing tools, and those existing tools don&amp;#x27;t &lt;i&gt;really&lt;/i&gt; suck, it&amp;#x27;s probably not worth migrating. It would take a lot of time and introduce significant new risks and operational complexity without a compensating payoff.</text></item></parent_chain></comment><story><title>Running Databases on Kubernetes</title><url>https://questdb.io/blog/databases-on-k8s/</url></story>