https://marktaguiad.dev/tags/argocd/ Recent content in Argocd on marktaguiad.dev Hugo en-us marktaguiad@marktaguiad.dev (Mark Taguiad) marktaguiad@marktaguiad.dev (Mark Taguiad) marktaguiad.dev Fri, 17 Apr 2026 00:00:00 +0000 https://marktaguiad.dev/post/ci-argocd/ Fri, 17 Apr 2026 00:00:00 +0000marktaguiad@marktaguiad.dev (Mark Taguiad) https://marktaguiad.dev/post/ci-argocd/ <p><div class="alert alert-info"> <div class="alert-title">Info</div> <div class="alert-content"> Read on related blog first; <a href="https://marktaguiad.dev/post/building-cicd">Building CI/CD Pipeline - A Not-So-Comprehensive Guide</a>. </div> </div> <img class="theme-image" src="https://marktaguiad.dev/images/devops/cicd/ci-argocd.png" data-light="/images/devops/cicd/ci-argocd.png" data-dark="/images/devops/cicd/ci-argocd-dark.png" alt="Architecture Diagram" > Traditional CI/CD pipelines tightly couple build, test, and deployment into a single workflow. Once a change passes tests, the pipeline pushes directly to the target environment. While simple, this model limits visibility, auditability, and control over deployments.</p> <p>This approach shifts deployment responsibility away from the CI pipeline into a dedicated GitOps repository, where the desired state of the system lives. Deployment is no longer “pushed” — it is pulled and reconciled by ArgoCD.</p>