Encrypt secrets with sops and age #373
Merged
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
dgauldie
reviewed
Mar 14, 2024
dgauldie
reviewed
Mar 14, 2024
dgauldie
reviewed
Mar 14, 2024
dgauldie
reviewed
Mar 14, 2024
dgauldie
approved these changes
Mar 14, 2024
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.
Description
As
kubesealonly encrypts kubernetes Secrets and we also need kubernetes ConfigMaps encrypted, andKSOPS(which is based onsopsbut makes decryption part ofkustomizeand not an explicit step otherwise - though you still need to encrypt withsops) has caught the eye Nisshant and is bundled with ArgoCD, I re-present thesopswithageencryption.In addition to working as before (save fetching a new key as detailed in the README.md) I have written a
get_secret_ui.shtool to help those that need a specific secret and find the hassle to be quite a drag.