feat: introduce encrypted volume store support #43
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 implements support for storing Docker registry secrets via an encrypted volume store.
When k2d is started with the
K2D_STORE_REGISTRY_BACKEND=volumeit will generate or retrieve the content of an encryption key under /var/lib/k2d/volume-encryption.key and use it to encrypt Docker registry secrets at rest.When this environment variable is not specified, k2d will use the previously introduced memory store for registry secrets (see #17)
These secrets are then decrypted when needed (e.g. to pull an image from a private registry or when inspecting them).
Related to #17