Repository navigation
v1.23.0: unlock encrypted nodes remotely
Highlights
nix run .#unlock -- <node>: unlock an encrypted node remotely
When a node's TPM doesn't unlock its disk (say, after a firmware update), the node waits in its boot stage. unlock reaches it over SSH, gives it the recovery passphrase from secrets.yaml, waits for it to boot, and enrolls its TPM again, so the next boot unlocks itself. It replaces the manual ssh -p 2222 and systemd-cryptenroll steps (#45).
The boot stage keeps the node's usual address
The boot stage's DHCP identified itself differently from the booted system's (DUID vs. MAC), so the router handed it another address each time. On a test node that was .130, then .132, never its usual .129, and remote unlock couldn't find it. It now asks by MAC and gets the node's usual address (#45).
Both were tested on real hardware (Beelink EQ12, Intel N100) with the TPM slot removed on purpose: the boot stage came up on the usual address, unlock unlocked the node and re-enrolled the TPM, and the next reboot unlocked unattended.
Monitoring: room for Prometheus
The light flavor's Prometheus used ~660Mi of its 768Mi limit on a 3-node cluster, and it grows while replaying its WAL after a restart. The limit is now 1536Mi (request 512Mi) (#48).
Docs: network boot on Intel N100 mini PCs
The firmware lists no PXE entry even with the network stack on, and pixiecore's chain-loaded iPXE hangs. iPXE with an embedded script (DHCP, then the installer over plain HTTP from another node) boots the installer fine (#49).
Upgrading
Nothing to change in vars.nix. An encrypted node gets the new boot stage with its next upgrade.