At work, I've been running Postgres instances in Kubernetes for years now. The setup makes a lot of sense for me within my work context. In the context of your

At work, I've been running Postgres instances in Kubernetes for years now. The setup makes a lot of sense for me within my work context. In the context of your one-man-show side projects, for the love of god, don't use Kubernetes. Kubernetes is a tool for a) having separate teams take care of the hardware and OS-level administration on one side, and application payloads on the other side, and for b) realizing high-availablity setups spread across multiple machines and multiple datacenters. None of that is going to apply to your side project in all likelihood. (You can still go with Kubernetes if you want to learn it and play around with it, but then that would be its own side project.)