Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

readme: mention limitation of backup with key renewal #1533

Merged
merged 2 commits into from
May 23, 2024
Merged

readme: mention limitation of backup with key renewal #1533

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
47bb72b
readme: mention limitation of backup with key renewal
willbush May 22, 2024
c59fe7a
Rephrase note
alemorcuq May 23, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -742,6 +742,8 @@ kubectl get secret -n kube-system sealed-secrets-key -o yaml >>main.key

> NOTE: This file will contain the controller's public + private keys and should be kept omg-safe!

> NOTE: After sealing key renewal you should recreate your backup. Otherwise, your backup won't be able to decrypt new sealed secrets.

To restore from a backup after some disaster, just put that secrets back before starting the controller - or if the controller was already started, replace the newly-created secrets and restart the controller:

* For Helm deployment:
Expand Down
Loading