that deals with the packaging of the artifact, the unit tests, security scanning, etc. And even post-deployment there are several actions (such as running smoke tests) that are not covered by today’s Argo on its own. For example, a very popular pattern for deployments is to have pre-sync and post-sync steps in a deployment pipeline. Sync pipeline A possible scenario for a pre-sync possibly rollback automatically if the metrics are not healthy). A possible scenario for a post-sync step is to perform smoke testing on the deployment that was just synced. Codefresh has great

CD provides Sync Phases and Waves to address other use cases ○ Three sync phases - Pre-sync, sync, post-sync ○ Within each phase can have multiple waves, next wave does not proceed until previous phase still required to manage SDLC ArgoCD Managed Deployment Pipeline Managed Deployment Pro Consistent Post-Test update of image reference Con Image reference updated in git before integration tests, manage

Weaveworks [1.6] is credited with pioneering the GitOps model. The story, de- scribed in a 2021 blog post [1.7], is very interesting. Back in 2017, Weaveworks was a Software-as-a-Service (SaaS) company that controller completes the deployment, a postsync hook can trigger additional pipelines to perform any post-deployment tasks. The model is illustrated in Figure 6-3. Figure 6-3: The CI-triggered and GitOps-owned