Garbage collection errors when deleting the secret before sealedsecret about sealed-secrets HOT 2 CLOSED

I guess this is expected behaviour, but maybe we should recreate the secret if deleted and there is a sealedsecret. What do we think the UX for this should be?

from sealed-secrets.

We should just ignore "not found" at this point in the code, as we just want to delete the Secret and don't really care "how" the secret was deleted.

Recreating the Secret if you delete it sounds like a separate feature request, and is worth discussing. I kind of feel like if you deleted the secret then you probably meant to for some reason and we don't need to "optimise" this. Currently I think the Secret will be recreated when the controller restarts (since it won't be able to tell the difference between that and the regular new-SealedSecret case). I would have said that was just fine for such a rare/ambiguous situation, but this was also one of only two questions asked of sebgoa after his demo at k8s community meeting - which makes me wonder if there's some importance here that I'm missing..

from sealed-secrets.