Holla die Waldfee. That update of Rook to v1.17.0 just crashed my three control planes for a solid 20 minutes. They definitely did not like that. High time for the new Pis to arrive.
Holla die Waldfee. That update of Rook to v1.17.0 just crashed my three control planes for a solid 20 minutes. They definitely did not like that. High time for the new Pis to arrive.
This Week in Self-Hosted (18 April 2025)
The latest from @homeassistant, software updates and launches, a spotlight on #Papra -- a new document management platform, and more in this week's self-hosted recap!
Rook has released a good one: https://blog.rook.io/rook-v1-17-storage-enhancements-5eb9a6abd1ea
Especially interesting for me is the ability to specify a bucket owner for a new OBC instead of having Rook create a new S3 uder for each OBC.
Also interesting: MONs behind a k8s service. This could be interesting to avoid hardcoded IPs in my Ceph client configs, making MON relocations a lot simpler.
NAS-Ersatz: Ein i5 Mini-PC ist unterwegs. Jetzt Konzeptarbeit.
Habe noch ein Gegenmodell zu Proxmox überlegt: Den Server mit Alpine Linux - wirklich minimalster Umfang - aufsetzen, und die diversen Dienste zumindest in eigenen Docker Compose Stacks laufen lassen. iobroker dann „bare metal“.
Spart den erheblichen Overhead von Proxmox aber hat natürlich kein „1 klick“ Snapshot, und mal eben mit wenig Risiko was Neues ausprobieren ist auch nicht so einfach.
#linux #proxmox #homelab
Phew yeah, my control plane instability is about as annoying during service updates as I thought. Almost every Helm chart update leads to a slew of timeouts and CP component restarts.
Luckily, the SSDs for the Pi5 have already arrived, and the Pis themselves are on their way.
At first I thought it was a late April Fools, but now I very much want one.
A rack-mountable beer fridge from 45drives!
I will have a 40U in the near future and not much to fill it in with, so maaaaybe?
What do you guys do with your left-over (public) IPv4 addresses? And no, that’s meant for real :)
I was mildly accepting of Synology "locking" their enterprise NAS equipment to their branded hard drives, since that's how enterprises tend to work. However, the next step in the enshittification of Synology has occurred. No more Synology equipment for me. https://www.tomshardware.com/pc-components/nas/synology-requires-self-branded-drives-for-some-consumer-nas-systems-drops-full-functionality-and-support-for-third-party-hdds
New blog post: https://blog.mei-home.net/posts/k8s-migration-25-controller-migration/
I like to think that many of my blog posts are mildly educational, perhaps even helping someone in a similar situation.
This blog post is the exception. It is a cautionary tale from start to finish. I also imagine that it might be the kind of post someone finds on page 14 of google at 3 am and names their firstborn after me.
Finally! Wireguard from laptop and smartphone back home to my NAS! I can now use navidrome and my music collection on the go. Turning off all the lights I forgot while leaving is a bonus! #homelab #wireguard
In den letzten Wochen habe ich mich, immer mal wieder, mit #NetBox beschäftigt. Es ist ein ziemlich komplexes Tool, aber unglaublich gut.
Die Videos von Viatto sind dabei eine extrem gute Hilfe das Konzept zu verstehen und einen guten Einstieg zu bekommen.
Cursed homelab update:
I now have a (slightly broken) PiHole!
Default settings only as it's settings are in an ephemeral volume, I want to put them in CephFS but can't, _yet_, as I need to check if Rook fucks with existing files in a CephFS it can add volumes to. I only have two CephFSes, and don't want to add anything permanent to #2 until I've verified that giving it access to #1 won't accidentally delete things.
I am being paranoid here and procrastinating, this is literally 10 minutes work and I've been putting it off for months as RBD volumes have been ideal for everything I've done so far.
Not me locally testing DeepSeek-r1 on a Raspberry Pi for reasons.
Nossirree.
Public Service Announcement: Accidently having TWO DHCP servers on one VLAN is not a good idea.
Just spun up an instance of obsidian live sync. The setup was and is pretty terrible, but once it works, it works.
Also spun up an instance of Standard Notes. I was excited to try it, but not only are there barely any docs on self hosting the web app, but some features are _still_ locked behind a $40/yr paywall on a self-hosted instance. I get it, the devs gotta make money. But putting markdown behind a subscription is wild
I don't want to say I'm persistent, but finally got a docker container building in a k8s Jenkins in my home lab!! Took a "few" tries and a lot of learning LOL