← Back to context

Comment by 9dev

12 hours ago

I know, it's supposed to spark excitement and make me long for Kubernetes, but… all I'm feeling is dread.

When our company was still small, I decided to go with Docker Swarm mode on Hetzner vServers to avoid the complexity of Kubernetes, until we've grown bigger™. Swarm mode got kinda-sorta-canceled, but by now I've built so much automation and architecture around it, it's working pretty stable, is super cheap to run, and doesn't involve too much maintenance.

Then again, demands are rising, and I'm starting to feel boxed-in by the hardware nodes the cluster runs on—I still need to account for the number of CPU cores to estimate the proper number of replicas for a worker container, for example. We also just got new funding, so this is probably the time I should finally be considering that Kubernetes migration, and do it properly once and for all.

But every time I reach this point, I start to dive into the documentation, the Big Cloud pricing charts, the upgrade procedures… I feel like I can avoid steering into the complexity maelstrom just a little longer.

> Then again, demands are rising, and I'm starting to feel boxed-in by the hardware nodes the cluster runs on—I still need to account for the number of CPU cores to estimate the proper number of replicas for a worker container, for example.

Have you switched to Hetzner bare metal? I'm pretty sure that'll raise your performance ceiling significantly.

> But every time I reach this point, I start to dive into the documentation, the Big Cloud pricing charts, the upgrade procedures… I feel like I can avoid steering into the complexity maelstrom just a little longer.

You can run k8s on Hetzner. Downside: Running k8s yourself. Upside: Not dealing with big cloud providers.