4 · CI/CD & GitOps

4. Declarative GitOps with ArgoCD & Progressive Delivery

Push vs pull CI/CD models, automated state reconciliation, and canary rollouts.

11 min read · 2 MCQs

The GitOps Control Loop

In traditional CI/CD (Push model), the build pipeline holds cluster administrator credentials. In GitOps (Pull model), an in-cluster agent (ArgoCD/Flux) continuously observes the Git repository and pulls changes, reconciling deviations automatically without exposing cluster credentials to CI.

Canary Releases & Rollbacks

Using Argo Rollouts, route 5% of traffic to a new version, evaluate Prometheus error rates and latency percentiles (p99 < 100ms) over a 10-minute analysis window, and automatically rollback if error thresholds are exceeded.

Chapter quiz

2 questions · pass mark 75%

1. Why is GitOps (Pull model) considered more secure than Push CI/CD?
2. In automated canary rollouts, what triggers a rollback?