• 0 Posts
  • 20 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle







  • The solutions you’ve mentioned aren’t exactly equivalent. Proxmox is a hypervisor while Docker Swarm and Kubernetes are container orchestration engines. For example, I use Proxmox in a highly available cluster running on three physical nodes. Then I have various VMs and LXC containers running on those nodes. Some of those VMs are Kubernetes nodes running many Docker containers.

    I highly recommend Proxmox as it makes it trivial to spin up new containers and VMs when you want to test something out. You can create and destroy VMs in an instant without messing with any of your actual hardware. That’s the power of a good hypervisor.

    For orchestration, I would actually recommend you just stick with Docker Compose if you want something very simple to manage. Resiliency or high-availability usually brings with it a lot of overhead (both in system resources as well as maintenance costs) which may not be worth it to you. If you want something simple, Proxmox can run VMs in a highly-available mode so you could have three Proxmox nodes and set any VMs you deem essential to be highly-available within the cluster.

    For my set up, I have certain services that are duplicated between multiple Proxmox nodes and then I use failover mechanisms like floating IP addresses to automatically switch things over when a node goes down. I also run most things in Kubernetes which is deployed in a highly-available manner across multiple Proxmox nodes so that I can lose a physical node and still keep (most) of my services running. This however is overkill for most things and I really only do it because I use my homelab to learn and practice different techniques.





  • I’ll let folks with more security experience dive into your specific question, but another option is to host your website on something like Github pages (using a static website generator like Jekyll) and point Cloudflare at it. That way you don’t need anything pointed at your local network, get the uptime of Github, and still benefit from your own domain name.

    That’s what I’m doing with my own blog and it’s been great. Github provides the service for free but if they ever charge for it I’ll just start hosting it locally.






  • Pihole is a big recommendation for me! It really changes the way you interact with the web. Home Assistant as well. If you’re at all interested in home automation it’s fantastic.

    If you’ve got an interest in privacy I’d recommend playing around with hosting SearXNG. And a new service I’m playing with is Immich. Think Google Photos but locally hosted, free, and open source.



  • For reducing power consumption (and thus heat), a simple improvement could be just switching to a headless Linux install instead of Windows. It’ll run much more efficiently for homelab workloads.

    Since you already have a UDM, I’d suggest just a simple port forward to expose your Minecraft server to the public internet. Yes, it will expose you to risk of attack by having anything public from your network, but as long as you keep your Minecraft server up to date you should stay covered security-wise pretty well. I’d suggest setting up a cronjob to restart the Minecraft server and check for updates every 24hr to make sure you’re always up to date.