-
Notifications
You must be signed in to change notification settings - Fork 684
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.
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
backup of my SealedSecrets doesn't work #923
Comments
Could you share your controller logs? |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Due to the lack of activity in the last 7 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
@alemorcuq can reopen this issue?we are facing the same problem, log is here. The secret sealed-secrets-key4gj4d is from old cluster, then i import it into the new cluster. It looks like the sealedsecrets have not been unsealed successfully. 2022/10/14 07:52:55 Starting sealed-secrets controller version: v0.12.5+dirty |
sorry,the problem is solved. After i has imported all secret key from the old cluster into the new cluster, sealedsecrets have been unsealed successfully. |
This might be related to #1260 |
Which component:
controller
Describe the bug
We did the backup of sealedsecrets keys of one cluster using
And then applied it to another
Did restart the controller too. But the secrets were not able to unseal - it kept complaining
no key could decrypt secret
I did try to decrypt manually and that worked
We also saw issues where it was decrypting few secrets fine while for others it gave errors
Expected behavior
Sealedsecrets should have been unsealed
The text was updated successfully, but these errors were encountered: