Replies: 2 comments
|
Seeing a similar issue |
0 replies
|
This happens very often for us too. The only way I know how to fix it is to delete the secret from ArgoCD and then instantly it goes healthy (because it recreates the secrets fine). |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
For some reason ExternalSecret resource gets deadlocked with state "secret already exists". I find it hard to reproduce as this issue happens c.a. 50% of times.
I'm not sure why this happens but my wild guess was that ExternalSecret pulls a secret from external repository and argocd treats it as "not mine" so it purges it and then some race condition happens?
I've also noticed in the logs following entries, note that they appear with 1 seconds difference, perhaps it is relevant.
All reactions