Tags: diegosanchez/sealed-secrets
Tags
Merge bitnami-labs#325 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 bitnami-labs#319 Co-authored-by: Marko Mikulicic <mkm@bitnami.com>
Merge bitnami-labs#314 314: Improve error reporting in case of missing kubeconfig when inferring namespace r=mkmik a=mkmik Closes bitnami-labs#313 Co-authored-by: Marko Mikulicic <mkm@bitnami.com>
Merge pull request bitnami-labs#304 from bitnami-labs/mkmik-patch-1 Update RELEASE-NOTES.md
PreviousNext