Build a GitOps Rollout Pipeline with ArgoCD Progressive Delivery
Overview
What this challenge is about.
Receive the current CI pipeline (GitHub Actions runs kubectl apply against EKS), one representative service (Go API, 8 replicas, 4ms p99 SLO, 0.1 percent error-rate SLO), and access to the cluster + Prometheus + Grafana. Stand up ArgoCD (Helm chart) + Argo Rollouts. Convert the service's Deployment to an Argo Rollout with canary steps (5/25/50/100), an analysis template querying Prometheus for the 2 SLOs, auto-pause on regression, and auto-rollback after 3 failed analyses. Document the GitOps repo layout (app-of-apps, base + overlay per env). Cut over the service, run a successful rollout and an intentionally bad rollout, both observed. Deliver the ArgoCD bootstrap + manifest, the Argo Rollout spec + analysis template, the GitOps repo, the failed-rollout evidence, the per-service playbook, and a 6-page CTO-facing memo.
The Brief
What you'll do, and what you'll demonstrate.
Stand up an ArgoCD + Argo Rollouts GitOps pipeline with progressive delivery and SLO-driven auto-rollback for one service, then ship the playbook for the remaining 24.
Earning criteria — what you'll demonstrate
- Stand up ArgoCD with the app-of-apps pattern and Helm overlays
- Convert Deployments to Argo Rollouts with canary steps
- Write Prometheus analysis templates that drive auto-pause + rollback
- Document a GitOps pipeline cleanly enough for the team to adopt
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
Careers
Roles this prepares you for.
Real titles. Real skill bridges. Pick the one closest to your trajectory.
Career mappings coming soon.