[amgad]

Progressive delivery lab

A 13-part hands-on lab that builds a progressive-delivery platform on local Kubernetes: canary, blue-green, traffic-routed and experiment releases, each gated by automated analysis on Prometheus metrics, with every change reaching the cluster through Git.

ROLE
"Author"
PERIOD
"Nov 2026"
STACK
"Kubernetes, Argo CD, Argo Rollouts, Prometheus, GitOps"
UPDATED
"Nov 2026"
github.com/amga-d/argo-rollout

Overview

Most bad releases still pass their health checks. The bug only shows in the numbers that matter to users: error rate and latency. This lab builds the platform that catches that, so a release promotes itself when the metrics are good and rolls itself back when they aren't.

I wrote it as 13 labs that start from an empty machine. It is pull-based GitOps end to end: a release is a commit to the desired-state repository, Argo CD polls it and reconciles the cluster, and nobody runs kubectl apply by hand. The sample workload is podinfo, which can inject errors and latency through environment variables, so a bad release is a one-line Git change.

What I built

  • App-of-apps bootstrap: one root Argo CD application installs Argo Rollouts, kube-prometheus-stack, a shared analysis library and Envoy Gateway, and an ApplicationSet picks up each workload.
  • Canary and blue-green Rollouts gated by AnalysisTemplates that query Prometheus for success rate and p95 latency per ReplicaSet.
  • Traffic-routed canary with the Gateway API plugin and Envoy Gateway: exact weights, and header routing for QA.
  • Failure drills: bad and slow releases that abort and roll back on their own, rollback with git revert, and CI from GitHub Actions that holds no cluster credentials.

How it fits together

    • release.shsimulated CI
  1. git push
    • GitHubdesired-state repo
  2. pulled every 60s
    • Argo CDapp-of-apps, minikube
  3. sync
    • Argo Rolloutscanary, blue-green
  4. AnalysisRun
    • Prometheussuccess rate, p95

Analysis passes: the release is promoted. Analysis fails: it is aborted and rolled back.

In the repository

$ git clone https://github.com/amga-d/argo-rollout.git

tree -L 1

.
├── exper/
├── labs/
├── error-count.yaml
├── README.md
└── tmux.sh

git log --author=amga-d --oneline -4

  1. bcc46cccustom envs, tools, scripts
  2. 72d2922fix: add intialDelay: 30s to the smoke job test /n bluegreen prePromotionAnalysis alawys fails because the smo
  3. be28535fix: use enable TLS for argocd-server
  4. 0a3ec4cInitial lab materials and instructions
  • Shell 100%