Status shows no key could decrypt secret for successful created secret about sealed-secrets HOT 14 OPEN

This appears to also be the same issue as #739 and #1354, #1355 , etc. :-(
Seems like the issue is hard to eliminate.

We're facing this even with 0.26.2, and on 0.25.0.
We were on 0.18.1 before that, which didn't have this problem.

from sealed-secrets.

I also found this problem on my sealed-secret installation while using ArgoCD, did you found the solution ? @Gnarfoz

from sealed-secrets.

Hey @WillyRL, there seems to be no permanent solution.
We work around it by restarting the Sealed Secrets controller pod from time to time.
During startup, it correctly marks all successfully unsealed secrets as healthy, as @alita1991 also wrote.

It seems like a trivial "out of order" thing...

from sealed-secrets.

Hey @WillyRL, there seems to be no permanent solution. We work around it by restarting the Sealed Secrets controller pod from time to time. During startup, it correctly marks all successfully unsealed secrets as healthy, as @alita1991 also wrote.

It seems like a trivial "out of order" thing...

It still not working on my setup, may I know your syncPolicy ?
My configuration:

      syncPolicy:
        automated:
          prune: true
          selfHeal: true
        syncOptions:
          - CreateNamespace=true
          - ApplyOutOfSyncOnly=true
          - ServerSideApply=true

from sealed-secrets.

I'm not sure what you're asking. This is not a problem with your ArgoCD configuration, it's a bug in Sealed Secrets.

from sealed-secrets.