Argo CD

Overview Nine weeks ago this series opened with a sentence I’ve been waiting to cash: “I’m building something in this gap. It isn’t ready to show you yet, and I’d rather earn the argument first.” Six posts later the argument is on the table — the missing middle, the PaaS bill at scale, golden paths over headcount, Argo CD and Kargo instead of a homegrown CD, secrets that never touch Git, and previews that promote. Every one of those posts was describing the same piece of software with the product name filed off. ...

Overview Last week’s post closed with a promise that was really four promises: preview environments per change, release trains where stable and canary share a namespace, weighted traffic splitting on Gateway API HTTPRoutes, and promotion gates between all of it. Honesty being the house rule of this series: two of those four are running in anger, and two are still designs. This post is about the real two — ephemeral previews and promotion — and ends with a straight account of the other two, because I’d rather correct myself than let a closing paragraph quietly become marketing. ...

Overview For three weeks I’ve ended every post with the same claim and never once shown my work. The claim: the CNCF ecosystem already solved continuous delivery, and what the mid-market team is missing isn’t technology, it’s the assembly — a golden path stitched from primitives that already exist. Argo CD reconciles. Kargo promotes. The last post argued you should adopt that road as a product rather than build it as a project. ...