Flashing Syncing every 3 seconds for out of sync app is annoying

[jsoref]

If you are trying to resolve an environment-specific issue or have a one-off question about the edge case that does not require a feature then please consider asking a question in argocd slack channel.

Checklist:

• [x] I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• [x] I've included steps to reproduce the bug.
• [x] I've pasted the output of argocd version.

Describe the bug

The flashing behavior of syncing every 3 seconds for an out of sync app is annoying.

To Reproduce

1. Install old sealed secret / upgrade it (see #5449)
2. Visit the sealed secret application
3. Watch the sync thing flash every 3 seconds

Expected behavior

I'm not really sure. I think at a certain point, I'd like it to stop flashing at me. It's good enough to tell me it knows it's unhappy and only tell me if it changes its mind instead of going through a 3s flash interval

Screenshots

https://user-images.githubusercontent.com/2119212/107208983-44019300-69d0-11eb-85fd-5da3e66f8af6.mov

Version

{
    "Version": "v1.9.0+bb15a49",
    "BuildDate": "2021-02-06T01:06:52Z",
    "GitCommit": "bb15a4996e327fb27ad91f3f6fa24f831f7754e0",
    "GitTreeState": "clean",
    "GoVersion": "go1.14.12",
    "Compiler": "gc",
    "Platform": "linux/amd64",
    "KsonnetVersion": "v0.13.1",
    "KustomizeVersion": "v3.8.1 2020-07-16T00:58:46Z",
    "HelmVersion": "v3.5.1+g32c2223",
    "KubectlVersion": "v0.20.1",
    "JsonnetVersion": "v0.17.0"
}

Logs

Paste any relevant application logs here.

[mabushey]

This sounds like it could be an issue I had after an upgrade caused by multiple controllers: https://github.com/argoproj/argo-cd/issues/5754

[jeffhoek]

We have observed the same behavior with ArgoCD v2.3.5 (part of OpenShift GitOps 1.5.4 operator) when there's an unresolved sync/diff between the live resource and what we have in Git. After resolving that inconsistency the constant Sync checking stops.

[emirot]

I had the same issue in my case it was because the Manifest was storing a field like that duration: 8760h and k8s stores like that 8760h0m0s by updating to what k8s expects it solved the issue.

[projx]

I had the same issue in my case it was because the Manifest was storing a field like that duration: 8760h

Sorry to drag up an old topic - but I've got the same issue occuring with Cert-Manager, could you provide clarity on how you fixed this specific one?

I was looking at using "ignoreDifferences", but I've spotted a couple of other pods with a similar issue (just different fields), and it is not long-term maintainable to add "Ignore" for everything.