-
Notifications
You must be signed in to change notification settings - Fork 691
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
325: Support parsing multiple private keys in --recovery-private-key r=mkmik a=mkmik When following the backup procedure outlined in our FAQ, the users tend to get one single YAML file that contains a `v1.List` object containing all the known sealing keypairs. This is actually a good thing, since kubectl makes backing up multiple secrets so easy. However, if the users pass such a file to --recovery-unseal --recovery-private-key it won't work since that command expects single secrets (either encoded as PEM or as json/yaml encoded v1.Secret objects). This change implements parsing v1.List of v1.Secrets (the output of `kubectl --namespace kube-system get secret -lsealedsecrets.bitnami.com/sealed-secrets-key -o yaml`) Closes #319 Co-authored-by: Marko Mikulicic <mkm@bitnami.com>
- Loading branch information
Showing
2 changed files
with
109 additions
and
17 deletions.
There are no files selected for viewing
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
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