How long does it take for ArgoCD to apply changes?

The time for applying changes in ArgoCD varies and depends on the following factors:

• Size and complexity of changes: Larger and more complex changes with many resources take more time to process.
• Cluster load: High node load and lack of free resources slow down the process.
• Synchronization settings in ArgoCD:
  • syncPolicy.automated: Enabling automatic synchronization speeds up, but does not determine the actual application time.
  • syncPolicy.syncOptions: Parameters like CreateNamespace=true or ResourcePruning=true can influence the time.
• Underlying infrastructure performance: Speed of etcd, network delays between ArgoCD and the Kubernetes cluster.
• Kubernetes cluster responsiveness: The API server and cluster controllers should process ArgoCD requests quickly.

In most cases, for regular applications, the time to apply changes in ArgoCD ranges from a few seconds to several minutes. For complex deployments or under high load, this time may increase.

To optimize application time, you can:

• Use automatic synchronization (syncPolicy.automated).
• Configure PreSync, Sync, and PostSync hooks to control deployment stages.
• Optimize Kubernetes cluster resources.
• Monitor the performance of dependent systems (etcd, network).