I have something similar to host paths with node selectors: an NFS provisioner for PVs. The provisioner is tied to the node with the large disk. It’s not resilient to node outages, but allows me to spread pods across the nodes. For my deployments, I’m preferring to use S3 storage wherever possible.

Excellent write-up. I had Nextcloud running on K3s with its files on a NAS which were shared with Minio and it worked well. I’m looking into Longhorn, but only have 2 nodes and it wants at least 3. I’m reevaluating my resiliency needs in favour of simplification.

I’ve been looking to do this, but haven’t found a good, easy to use pull thru proxy for docker, ghcr.io and some other registries. Most support docker only.

This one looks promising but overly complicated to set up.

A few times now, I’ve gone to restart a container and the repo’s been moved, archived or paywalled. Other times, I’m running a few versions behind and the maintainer decided to not support it, but upgrading would mean a complete overhaul of my Helm values file. Ugh!

I was considering a docker registry on separate ports for each upstream registry I’d like to proxy/cache.