K8s prob overkill if it’s just you and your family
Comment on v2.0.0: Stable Release of Immich (complete with Merch and DVD)
rumba@lemmy.zip 3 weeks ago
God damnit, now I need to set up k8s and install it.
I’ve been putting off moving out of Google photos for years. No, no, I shouldn’t spend the time to host it. It has that scary banner.
Way to ruin my weekend! /s
Congrats Immich Team! /and if you’re listening, thanks!
mmmac@lemmy.zip 3 weeks ago
rumba@lemmy.zip 3 weeks ago
K8s is pretty cheap for fault tolerance
Two VM’s and two Pi
If my wife decides whe wants to watch the wedding video or the kids first TKD break and it’s down, she’ll clamor to move back to Google/Apple. I can also move my piholes over there and some of my arr stack.
Resillient hosting for zero cost is pretty hot.
mmmac@lemmy.zip 3 weeks ago
If fault tolerance is what you’re looking for I’d suggest a minipc over a pi, specced higher for the same cost and muuuch more reliable long term in my experience
rumba@lemmy.zip 3 weeks ago
The nodes go on x86. You use the pi’s for control planes. They sit around doing pretty much nothing until a pod get’s wrecked or upgraded then they spin a new one. You use 3’s or 4’s clocked down to save power.
You really only need one, but for $50 two gives your fault tolerance, fault tolerance.
possiblylinux127@lemmy.zip 3 weeks ago
Two nodes doesn’t provide quorum
billwashere@lemmy.world 3 weeks ago
Whew… I was thinking it may have
nucleative@lemmy.world 3 weeks ago
There’s a really nice Google Take-Out parser for immich that will preserve all your meta data during import. It was kind of a dream to use, it worked so smoothly.
In my case, I moved about 100k photos and videos, and I’m still periodically finding old flash drives and SD cards laying around that were never imported, so im using the migration to catch up on decades of photo archival. So far, all good.
fruitycoder@sh.itjust.works 3 weeks ago
If you have linux on machine(s) k3s/rke2 is pretty easy to get going.
Decipher0771@lemmy.ca 3 weeks ago
I was going to finally do k0/k3 or something kubernetes to set it up. I managed to get it going scalable with just docker swarm. So the kubernetes procrastination survived another deployment!