Re-encrypting secret created with old .pub file from old controller --> with new encryption key from new controller about sealed-secrets HOT 4 CLOSED

If you have the old key, you're supposed to be able to do something like the link below.

How it's supposed to work is this #842

however, it's busted for me.
error: couldn't get version/kind; json parse error: json: cannot unmarshal string into Go value of type struct { APIVersion string "json:"apiVersion,omitempty""; Kind string "json:"kind,omitempty"" }

from sealed-secrets.

hi @uceimmp
as @cccsss01, if you have the old keys you can use the feature defined in #842. If you don't have the old keys, it is not possible to decrypt them.

If you redeploy in the same cluster without deleting all the resources, the controller will detect the old keys generated by other Sealed Secrets Controller. If you don't have any old resource, it is really complicated.

from sealed-secrets.

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.

from sealed-secrets.

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.

from sealed-secrets.