initializer: move cryptsetup image into initializer #1161
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 PR introduces the two commits of #1132 again, which have been reverted due to the release problems in #1150 .
Until now, we used a specific cryptsetup image, containing a couple of filesystem and mount tools that facilitate the LUKS encryption.
This PR is a first step to include the dependencies of the cryptsetup image in the initializer, while still keeping the bash entry point for now to allow setting up the LUKS device by the initializer. Thus all existing references to the specific cryptsetup image are dropped as part of this PR.
As a follow up the mounting/set up of the encrypted volume done by the bash entrypoint will be moved to a subcommand of the initializer binary.
K3s-QEMU-TDX: https://github.com/edgelesssys/contrast/actions/runs/12748493847
K3s-QEMU-SNP: https://github.com/edgelesssys/contrast/actions/runs/12748490036
AKS-CLH-SNP: https://github.com/edgelesssys/contrast/actions/runs/12748475625