Chapter 5. Synchronizing Applications
Argo CD’s synchronization process makes it easy to be able to take Kubernetes resources stored within Git or Helm repositories and apply them to a target cluster. Given that this capability is one of the core features of Argo CD, there are a variety of options available for determining when the synchronization process will be triggered and how the Kubernetes resources will be applied. This level of control is important, as there may be a need to guard exactly how and when content is applied (for example, if certain resources need to be applied in a specific order). In this chapter, we will explore the options available when synchronizing Argo CD Applications, their impact against the lifecycle of the application itself, the Argo CD server, and ultimately the target Kubernetes cluster.
Managing How Applications Are Synchronized
Given that the synchronization of content from source to target Kubernetes cluster is a fundamental concept in Argo CD, it is important to first understand the defaults that Argo CD applies and the various levels of customizations that are available. If you recall in Chapter 4, we briefly introduced synchronization and covered how the configurations can be defined within the .spec.syncPolicy property of an Application.
By default, when Applications are created, none of the rendered resources are applied to the Kubernetes cluster. This may surprise many new Argo CD users given that Argo CD is a tool that manages assets ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access