this post was submitted on 28 Nov 2023
2 points (100.0% liked)

Self-Hosted Main

504 readers
1 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
communick@selfhosted.forum
2
Good VPS solution for off-site self hosted stack (alien.top)
submitted 11 months ago by SillyLilBear@alien.top to c/main@selfhosted.forum
1 comments fedilink hide all child comments
 

I am looking to move a bulk of my docker containers offsite and use wireguard to access them. Anyone doing this with good success can recommend a provider? I am thinking about a 4 core 8g VPS from OVH which I think should be enough as that's roughly why my proxmox vm is.

I think a dedicated server is overkill for now.

Ideally, I would like to do k3s with the offsite the master with my LAN backup nodes, but I am not sure I want to get into that head ache for now, I can spin up another node and restore backups pretty quickly if needed.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] chin_waghing@alien.top 1 points 11 months ago

I've had hit and miss success with OVH. For some reason K3s would fail to install with some weird errors on their infra. This is probably fixed now.

If you intend to use OVH, get familiar with their Openstack UI and then Openstack terraform provider as it makes storing everything in git and state alot easier.

Hetzner I've not personally used, but lots of people preach about it.

โ€‹

RE K3s. Maybe I suck at english but from what you're saying it sounds like you want to host the control plane for k3s on prem and have a VPN to the nodes on the cloud? I would avoid this, Kubernetes gets a little funky when high latency, pod status may not be reported properly etc.

If that's not the case and you have the entire k3s cluster on your cloud provider of choice, then you'll be fine. One thing to note is Load balancing etc on your own cluster on a cloud provider can get a little tricky, but if you plane to just use kind: service with type: ClusterIP or using nginx ingress or traefik on the lan on the cloud provider, and connect the 2 networks (home and cp) via VPN, you could get away with no fiddly LB.

If you're not 100% set on k3s and rolling your own k8s, use the cloud providers managed solution, as they make life a little easier with things like storage CSI dirvers and LB controllers.

I hope this helps at all? This was quite a word vomit so sorry if this just ruined everything