Skip to content
refplat

Learn: Delivery

How a built, signed image becomes a running workload across every stage — via GitOps, a health-gated promotion ladder, and progressive (canary) rollout. This zooms in on the middle of The Life of a Deployment.

Audience: platform engineers who operate or extend delivery. Developers only need the “2-minute view” at the end of the orientation. Already fluent in ArgoCD + Argo Rollouts? Skip to the Reference.

Before you start: the domain model (Product / Environment / Stage) and ideally Life of a Deployment.

Read in this order

Section titled “Read in this order”
  1. Orientation — the one idea (you move a digest up a ladder; reconcilers converge each rung), the three reconcilers (auto-promoter · ArgoCD · Rollout), and a real alpha-shop climb from dev to prod.
  2. Reference — look-up: the Release schema, the per-Product ApplicationSet, the promotion paths and the ladder, the Rollout canary, the gotchas that bite, and a glossary.

Then, to go deeper on the real system

Section titled “Then, to go deeper on the real system”