Argo CD
Hard
GitOps Workflows
Automated sync without selfHeal succeeded on commit abc123, then a controller changed a field and the app went OutOfSync. What does Argo CD do next?
Select your answer:
Show answer and explanation
Answer: It does not sync until a new commit or parameter change
Explanation
Automated sync attempts one sync per unique combination of commit SHA and application parameters. If the last successful sync already used that commit and those parameters, Argo CD does not sync again. Only with selfHeal: true does it sync again after the self-heal timeout, which defaults to five seconds.
More hard Argo CD questions
- In Argo CD 3.6, which ignore rules can the argocd.argoproj.io/ignore-differences annotation on a resource contain?
- An extra resource carries argocd.argoproj.io/compare-options: IgnoreExtraneous and turns Degraded. Everything else matches Git. What does the app report?
- What is a Sync Wave in Argo CD?
- How does Argo CD handle Kubernetes secrets?
- Which of the following is NOT a valid sync strategy in Argo CD?
- What is the purpose of resource hooks in Argo CD?