• 0 Posts
  • 71 Comments
Joined 2 months ago
cake
Cake day: March 24th, 2026

help-circle







  • I think software subscriptions are a scam, but I don’t mind buying a perpetual license that is only good up to a certain version with additional fees for newer versions. It’s also fair to charge a recurring fee for something that has recurring hosting costs like a VPN, cloud storage, etc.

    If they weren’t such dipshits, the “lifetime pass” should have been a perpetual license you can keep using as long as you want, but charge an optional fee for newer versions if you want to upgrade and get more features. They should also have offered a hosted service to make your instance available to others and charge a monthly fee for that. I think people would’ve been fine with all that.





  • I run k3s on a single node and it’s not really that much more overhead than Docker Compose if you understand k8s. I mostly have a deployment.yaml, service.yaml, ingress.yaml, and network-policy.yaml for each service that I’ve copy / pasted and updated. Here are some of the benefits over Docker Compose for my setup:

    • Has a built-in Traefik reverse proxy / ingress controller so I can access my services by domain name instead of by port, like http://jellyfin.lan/, http://forgejo.lan/ (using local dns on my OpenWRT router)

    • I use the Calico CNI so I can have network policies for each service to allow them to access only what they need. If a service doesn’t need internet access, it doesn’t get it.

    • I use Bitnami Sealed Secrets to store my secrets in YAML files that can be safely stored in git

    • ConfigMaps make it easy to manage configuration files

    • Easier to have separate YAML files for each service while sharing a network between them. Services connect to each other like http://forgejo.forgejo.svc.cluster.local/

    Of course, if you’re looking to load balance across multiple machines, k3s makes even more sense.

    Edit:

    k8s is the clear industry standard for container orchestration at this point, so if you want something beyond Compose, a lightweight k8s distribution like k3s is an obvious choice.