this post was submitted on 03 Jul 2026
13 points (93.3% liked)

Selfhosted

60366 readers
666 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.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

I'm looking for some actually working examples of using Flux to deploy at least Immich and Jellyfin with Traefik ingress using Flux CD preferably that use NFS shares for storing data and/or configs, and prometheus monitoring. I've found a few just from searching, but usually it seems like they aren't actually working, just demonstrating something.

Also, what UI do you use for Flux?

Some background: I use k0s with MetalLB and Longhorn and all db storage on a separate postgres server. I've gotten a good repeatable installation of all of that as well as the FluxCD Operator via kOsctl and helm charts which allows me to simply launch k0sctl and provide it a single config that is well documented that deploys all of that across all of the servers. But Flux has been a challenge, especially since I don't really care to learn Kustomize. I already have lots of other things to learn, LOL.

I want to avoid having to use lots of CLI commands that I then have to make sure to document and takes a while to remember all of the issues that can come up and all of that. I'm basically looking for easy disaster recovery. All files and configs are stored on a NAS that is then a single point of all offsite backups. It has worked well with docker, but I want better dynamic distribution of services to take better advantage of the few small servers I have. And docker Swarm ended up being difficult to implement with a lot of applications, and I don't trust Docker not to further enshitify as well as the number of GUIs that support it well is limited, mostly just to Portainer which has been also enshitifying lately. So I've been looking to k8s.

you are viewing a single comment's thread
view the rest of the comments
[–] scrubbles@poptalk.scrubbles.tech 1 points 15 hours ago* (last edited 15 hours ago)

I don't use flux or traefik, but if you're interested I can show you how I set up Istio.

As for commands, that's why you should learn either kustomize or helm or something. The huge benefit of kubernetes is infrastructure as code. You write it in yaml and then don't need to remember how to do it again.