Question

Your team uses Argo CD to deploy a microservices application. The application requires that a database migration Job completes successfully before the API Deployment starts, and a namespace-level ConfigMap must exist before either. All resources live in the same Git repository under one Application. What is the recommended Argo CD mechanism to control the order in which these resources are applied during a sync?

Accepted Answer

Add sync-wave annotations to the resources so Argo CD applies them in ascending wave order

Answer

Split each resource into separate Applications and manually sync them one at a time in the UI

Answer

Set the Application's syncPolicy to automated with prune enabled to force sequential ordering

Answer

Rely on Kubernetes to automatically detect resource dependencies and apply them in the correct order