PlatformEngr® Progressive delivery course

Progressive delivery: printable course notes

Blue-green and canary releases with Argo Rollouts on the Argo CD platform: install from Git, migrate a Deployment, blue-green with a preview, analysis templates on Prometheus, a self-rolling-back canary, Istio and Gateway API traffic routing, team operations, and a failed-release drill.

These pages are the same content as the interactive course, on one page per module, for reading and printing.

Four pieces

PieceWhat it is
See the end resultNot the first step: a 30-minute preview of a canary that rolls itself back when its error rate climbs, with few explanations.
Full course10 modules on the setup you built in the Argo CD course: Argo Rollouts, blue-green, analysis with Prometheus, a canary that rolls itself back, Istio and Gateway API traffic, team operations and a failed-release drill.
Reference repoThe finished implementation: the three repos as they look at the end of this course, plus the docs. You copy from it.
Your three reposargocd-platform, checkout-app and checkout-config from the Argo CD course. This course changes all three.

Your setup

Commands in these notes use these values (shared with the interactive course, stored only in this browser).

Outline

ModulePartTimeYou areYou will
00 Orientation: deploy is not releaseFoundations20 minPlatform and productKnow what progressive delivery adds to the Argo CD setup you already run, check your tools, and confirm (or rebuild) the end state of the Argo CD course.
01 Install Argo Rollouts from GitFoundations25 minPlatform teamInstall a pinned Argo Rollouts controller and its read-only dashboard with an Application and values in Git, and find your way around the dashboard and the kubectl plugin.
02 From Deployment to RolloutFoundations40 minProduct teamRelease checkout chart v2.0.0, in which the Deployment is a Rollout, ship a new version to dev as a canary that waits for a person, promote it, and handle an aborted release through Git.
03 Blue-green in devReleases judged by metrics30 minProduct teamRun dev as blue-green: every new version comes up as a full copy behind a preview host, waits for a person, and replaces the old one in one switch.
04 Metrics and analysis templatesReleases judged by metrics40 minPlatform teamInstall a small Prometheus and a load generator from Git, write the platform's shared success-rate check as a ClusterAnalysisTemplate, and let it promote (or stop) dev's blue-green releases.
05 Canary with automatic rollback in prodReleases judged by metrics35 minProduct teamRun prod as a stepped canary with background analysis, ship a good release that walks through the steps alone, and a bad one that aborts itself at the first step.
06 Istio: exact weights and header routesTraffic50 minPlatform and productInstall Istio from Git, put prod and the load generator in the mesh, and release checkout with exact 5% steps, a header route for testers, and mutual TLS required in prod.
07 Gateway API: the lighter optionTraffic30 minPlatform and productRelease dev as a canary that splits traffic at the edge with the Gateway API on Traefik and the Argo Rollouts Gateway API plugin, with no mesh, and know when each kind of routing fits.
08 Operate releases with teamsOperate30 minPlatform and productLet team-checkout resume, abort and retry its own releases from Argo CD and nothing more, send every finished or aborted release to a release log, abort releases stuck past their deadline, and write the release runbook.
09 Capstone: the failed-release drillOperate45 minPlatform and productHandle a release that every check passes and users still feel: notice it, roll it back fast, add the missing check, prove it catches the next one, write the incident, and put catalog on a canary too, without step-by-step commands.

The release path

  1. Committed: A new version or setting in Git
  2. Deployed: New pods run, users not there yet
  3. Exposed: A share of users, a header, a preview host
  4. Measured: Prometheus: errors and latency of the new pods
  5. Decided: Analysis or a person: go on or abort
  6. Promoted: All traffic on the new version
  7. Rolled back: Abort, then a revert in Git

Where the cluster runs

kind on your laptop is the default for every module. On an existing cluster, use your Argo CD hostname for the CLI; the rest is the same.

Between you and production