How long does Argo CD usually take to deploy changes to the target system?

The time required for Argo CD to deploy changes to the target system depends on several factors:

• The size and complexity of changes in Kubernetes manifests
• The number and state of resources in the cluster
• System and network load

In typical cases, Argo CD starts applying changes almost immediately after detecting updates in the repository (usually with a delay of a few seconds). The synchronization and application process can take from a few seconds to several minutes.

For example, for small applications with a few pods, deployment time usually ranges from 10-30 seconds. For larger and more complex systems with many resources, it may take longer.

It is important to understand that Argo CD acts as a controller that constantly monitors the state and strives to bring it into compliance with the description in Git, so the deployment time is the time until the desired state is reached, not instant application.