How can I automatically sync Argo Workflows WorkflowTemplates that are managed by ArgoCD? #20079
Unanswered
tonikarppi
asked this question in
Q&A
Replies: 1 comment
-
I would open an issue with a minimal example to reproduce this. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi. I'm trying to use ArgoCD to manage Argo Workflows WorkflowTemplate resources, but I'm having issues where ArgoCD reports that the state is synced whenever I make changes to the spec.
I'm using app-of-apps pattern, where the app that deploys the templates looks similar to:
The target path in the same repo contains the kustomization file with the WorkflowTemplate resources. When I make a change to the spec in the WorkflowTemplate, I can see that the new commit is detected in the "SYNC STATUS" section of the UI, but the "LAST SYNC" section still shows the previous commit. The UI never changes to out-of-sync, it just stays in Synced status. However, if I compare the live manifest and the desired manifest, I can see the changes in the desired manifest that are not present in the live manifest. If I manually click on the sync button, then the changes are applied as expected.
I can make the application go out of sync by editing the metadata, for example adding an annotation to the WorkflowTemplate resource. I assume this has something to do with limitations regarding managing the state of CRD resources. I'm wondering if there's a way to make ArgoCD sync the application any time there's a change to the generated resources? Changing the annotation every time I make a change to a WorkflowTemplate resource does not seem like a great solution.
Beta Was this translation helpful? Give feedback.
All reactions