[heipei]

Seconded. Every three months I get a little anxious about not running on one of the clouds that would let me scale more quickly (and also would let me do things like use Athena to go through a huge S3 bucket). But then I do a little math and realise that the bandwidth bill from AWS alone would eclipse all of my hosting costs at Hetzner, not to speak of the actual servers running there, and I don't really need fast scaling if I can just provision everything with a nice margin (2x) and still come out way below AWS prices. But it really depends on the nature of your business I suppose.

[hughrr]

Bandwidth on AWS has some scary side effects if you're not careful. A former colleague of mine got screwed for this and S3. Backup storage costs? $57 a month. Just the bandwidth fee to do a restore? $450

[schoolornot]

If only deploying Kubernetes was as simple as running a golang up and etcd tolerated some latency, you could spin up a node in AWS, another in Hetzner, and a third in DigitalOcean.

[pas]

Try microk8s.io , it uses dqlite (replicated SQLite + raft leader election; also, yes, it needs 'snap', just let it go, it doesn't matter). Use a fixed version stable channel, because they apparently employ the world's eminent simian scientists to break your cluster on every major update. Even on a test cluster don't be too frugal with RAM.

https://ubuntu.com/tutorials/getting-started-with-kubernetes...