3 ms·
Exactly! I had a three node k3s cluster hosted on OVH. When I decided to switch to Contabo, it was as easy as adding the three Contabo nodes to the cluster, and
by arcastroe 2y ago
Exactly! I had a three node k3s cluster hosted on OVH. When I decided to switch to Contabo, it was as easy as adding the three Contabo nodes to the cluster, and then removing the three OVH nodes (plus updating some DNS rules). It was the easiest and simplest migration I'd ever done. All my services and data just moved automatically and mostly with zero downtime. The only service that experienced a little downtime was Plex, which as I understand does not support high availability. If I ever find a cheaper host, I'll simply switch over. No hassle and no vendor lock in.
- lysp 2y agoThis is what I also want to do. How are you handling storage? That is the only issue I'm struggling with for a small 3-node deployment.
- arend321 2y agoThat's indeed the pain point. Distributing a stateless app is relatively easy. Distributing the shared file system and database over a remote, higher latency, cross-cloud setup is hard.
- WildGreenLeave 2y agoI run everything on Longhorn, including databases. Not the highest iops but definitely worth the hit for the easy of migrating.
- arcastroe 2y agoLonghorn volumes automatically replicate to multiple nodes (configurable) and automatically move to the nodes whose pods need it. A postgres database running on a single node will experience some downtime during (re)deployments or when moving across nodes, but should be pretty quick depending on the size of the database. For true HA database, CockroachDB is supposed to be compatible with postgres, but I haven't had a chance to play with it.
- 5Qn8mNbc2FNCiVV 2y agoHow's the performance with Longhorn with databases?