Contrary to my hopes in the previous post, Vault did not magically come back up again. I’m not sure why, but the ZVols created on TrueNAS by the previous cluster had truly gone away: thanks to zfs get, I could see that the creation times of all iSCSI ZVols was in the last week or so, i.e. while I’ve been rebuilding, not from the previous cluster. I guess when the StorageClass was deleted, it also wiped out all associated ZVols? That doesn’t quite ring true to me, as the cluster itself was inoperable due to unavailability of the Cluster Config (which was stored on an NFS mount on the drive that failed) - but, eh, can’t argue with results. The data was gone¹, so, time to rebuild!

Continuing my pattern of writing “week"notes every fortnight. It’s not intentional, I swear, it’s just working out that way!

Looks like I’m averaging about one “weeknotes” post every two weeks. That’s actually not too bad!

I just set up a step in my publication pipeline to automatically post on Mastodon when I publish a new blog post.

In my previous post, I had figured out how to inject Vault secrets into Kubernetes Secrets using the Vault Secrets Operator. My runthrough of the walkthrough worked, but I swiftly ran into namespacing issues when trying to use it “in production”.

Continuing my recent efforts to make authentication on my homelab cluster more “joined-up” and automated, this weekend I dug into linking Vault to Kubernetes so that pods could authenticate via shared secrets without me having to manually create the secrets in Kubernetes.