Hacker News new | ask | show | jobs
by dimitar 727 days ago
I would normally avoid recommending k8s, but perhaps the founder already was pretty comfortable with k8s from a previous job and knows what to avoid.

There are no production dbs in k8s, no service meshes, monitoring is only side-cars that send data to an off-cluster backend,

The automatic deployment with flux seems pretty nice!

1 comments

Having learnt k8s once, I found out it greatly simplifies things for me when I want to run new projects, even if it's single server only (there I use k3s).

Especially if there's a chance I need to run more than one client, or environment, on a given server, which is more important for "solo" enterprise than for a bigger company because I do not have money or time to care of multiple servers.