Submitted 2 days ago by lukkon@piefed.social to selfhosted@lemmy.world
Hi I got home assistant, immich, jellyfin and recently tried to set up next cloud with helm. Not everything is as smooth as I expected.
Do you guys have any other ideas for similiar setup on local kubernetes cluster?
Honestly, I avoid helm charts as much as possible. My preference is raw manifests + kustomize, deployed by Argo
What k8s distro? (Vanilla, k3s, rke2, minikube, harvester, whatever redhats open source open shift is called, etc?) What issues?
K3s
That’s a good one ARM or x86?
Helm sucks. You don’t even need it for what you’re trying to do.
Helm has worked well for me, what’s the problem you had?
Mostly pv provisioning and db setups. I use my external hard drove as k3s storage and e.g. for immich I failed to provide custom path (k3s/immich-media), it always complaints about some access rights.
So you have a classic issue of datastorage on kubernetes. By design, kubernetes is node-agnostic, you simply have a pile of compute resources available. By using your external hard drive you’ve introduced something that must be connected to that node, declaring that your pod must run there and only there, because it’s the only place where your external is attached.
So you have some decisions to make.
First, if you want to just get it started, you can do a hostPath volume. In your volumes block you have:
volumes: - name: immich-volume hostPath: path: /mnt/k3s/immich-media # or whatever your path is
The gotcha is that you can only ever run that pod on the node with that drive attached, so you need a selector on the pod spec.
You’ll need to label your node with something like kubectl label $yourNodeName anylabelname=true, like kubectl label $yourNodeName localDisk=true
Then you can apply a selector to your pod like:
spec: nodeSelector: localDisk=true
This gets you going, but remember you’re limited to one node whenever you want data storage.
For multi-node and true clusters, you need to think about your storage needs. You will have some storage that should be local, like databases and configs. Typically you want those on the local disk attached to the node. Then you may have other media, like large files that are rarely accessed. For this you may want them on a NAS or on a file server. Think about how your data will be laid out, then think about how you may want to grow with it.
For local data like databases/configs, once you are at 3 nodes, your best bet with k3s is Longhorn. It is a HUGE learning curve, and you will screw up multiple times as a warning, but it’s the best option for managing tiny (<10GB) drives that are spread across your nodes. It manages provisioning and making sure that your pods can access the volumes underneath, without you managing nodes specifically. It’s the best way to abstract away not only compute, but also storage.
For larger files like media and linux ISOs, then really the best option is NFS or block storage like MinIO. You’ll want a completely separate data storage layer that hosts large files, and then following a guide like this you can enable mounting of NFS shares directly into your pods. This also abstracts away storage, you don’t care what node your pod is running on, just that it connects to this store and has these files available.
I won’t lie, it’s a huge project. It took about 3 months of tinkering for me to get to a semi-stable state, simply because it’s such a huge jump in infrastructure, but it’s 100% worth it.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| Git | Popular version control system, primarily for code |
| NAS | Network-Attached Storage |
| k8s | Kubernetes container management package |
[Thread #63 for this comm, first seen 5th Feb 2026, 17:20] [FAQ] [Full list] [Contact] [Source code]
cymor@midwest.social 2 days ago
Prometheus and Grafana ElasticSearch Fluentbit and Kibana