feat: add zfs-service to zfs extension (unmount, encryption) #513
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch adds a new service to the zfs extension (
zfs-service
) that handles pool import and unmount. These operations are tied to the service lifecycle: the service imports all pools when it starts, waits for an exit signal, then unmounts all pools before exiting.As a subtle additional benefit, the service passes the
-l
flag tozpool-import
1, which instructs it to request encryption keys for all encrypted datasets. Using the zfskeylocation
2 property and Talos secure boot and TPM disk encryption, a ZFS encryption key file can be safely stored on the EPHEMERAL partition to import encrypted datasets at boot. Alternatively, a key can be stored on an https server.Footnotes
https://openzfs.github.io/openzfs-docs/man/master/8/zpool-import.8.html ↩
https://openzfs.github.io/openzfs-docs/man/master/7/zfsprops.7.html#keylocation ↩