When I got laid off I got really lucky and had an offer pretty quickly. After I got my homelab up and running, I decided to put some of my severance toward a new NAS, and upgade my storage. I moved the original off site, and installed Syncthing on both of them to keep a redundant copy of my most crucial data.
The old NAS has about 1/4 the storage of the new one, so I decided to be selective with the media I synced to it, so that the stuff that was the most important would have a backup, but the rest wouldn’t fill it up.
It isn’t particularly sexy, but one of my favorite things about my k3s homelab is that I took the time early in its creation to get proper HTTPS certificates, and automate their renewal. I think it’s great that all the top-shelf browsers require sites to use HTTPS, but it’s a nightmare for self-hosting when you have to click through several pages of warnings to hit any of your own services.
When I bought my first house ten years ago, I had just moved 750 miles via UPS. I boxed up and shipped what few belongings I cared to keep and then I got on a plane with all of my clothes; giving away, selling off, trashing, or otherwise abandoning on the curb what little furniture & large electronics I had.
The furniture in the new house was either handed down to me, or it came from the clearance section of the cheapest furniture store in town.
When I got laidoff last year and started building out my homelab , I upgraded my NAS from 8 to 32TB. As part of the new NAS setup I created two shares with quotas, which together are limited to 8TB; the size of the old NAS. I took the old NAS and a raspberry-pi with Tailscale installed to my folks’, and added a cronjob to my k3s cluster to sync those shares.
After I got laid off last year , I built a home lab k3s cluster to keep my skills sharp while I was job hunting. Initially I kept all the manifests in a mono repo, but I decided to break it up into micro services repos. This solved several problems, but it created another: I want to be able to link to it easily.
When I broke the mono repo apart, I did have the presence of mind to give each micro service repo a templated name: “homelab-” (eg homelab-metallb ).
Update It turns out the awk solution had a big problem I didn’t notice until after I posted this. The gist is that awk is only looking for --- or kind:, and it’s processing the file one line at a time. Once I inspected the contents of a file I had generated with the original script, I realized its apiVersion was in a different file, and then some other resource’s apiVersion was at the bottom of the file I was looking at.