07 - sync phases and sync waves

Argo CD executes a sync operation in a number of steps. At a high-level, there are three phases pre-sync, sync and post-sync. Within each phase you can have one or more waves, that allows you to ensure certain resources are healthy before subsequent resources are synced. Synchronization can be configured using resource hooks. Hooks are ways to run scripts before, during, and after a Sync operation. Hooks can also be run if a Sync operation fails at any point How Does It Work? When Argo CD starts a sync, it orders the resources in the following precedence: - The phase - The wave they are in (lower values first) - By kind (e.g. namespaces first and then other Kubernetes resources, followed by custom resources) - By name We're going to use some different examples and scenarios to see how sync phases and waves work 00:00 Sync Phases Overview 00:07:20 Sync Phases In Practice 00:41:55 Hook Deletion Policies Overview 00:46:25 Hook Deletion Policies In Practice 00:54:00 Sync Phases Overview 00:59:45 Sync Phases In Practice 01:06:36 precedence in the resources by kind and name ــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــ You can Follow Mohammad from on other platforms: Linkedin : https://www.linkedin.com/in/mohammad-madanipour-87149bb3 Github: https://github.com/mohammadll ــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــ You can follow our Channel on other platforms: Github: https://github.com/devopshobbies Likedin: https://www.linkedin.com/company/devopshobbies