Vol. IV
Release Engineering & DevSecOps Governance
Progressive delivery, GitOps, the DORA metrics at scale and framework governance
§ 01, What it's about
Progressive delivery, feature flags, GitOps at scale and the governance that makes release orchestration survive an audit. The Release Orchestration Framework is the skeleton; the examples come from my zero-touch release work at SWIFT.
§ 02, What I want the reader to be able to do
- 01
Promote a release through canary stages and roll it back without a meeting.
- 02
Run GitOps for many teams and know when a cluster has drifted from git.
- 03
Explain a release orchestration programme to an auditor with the evidence it produced.
§ 03, The diagram I keep coming back to
Scrolls sideways →
§ 04, Planned structure
- Part I
Progressive delivery engineering
Deployment strategies, automated canary promotion and rollback, and database changes that do not take the service down.
- Part II
Feature flag architecture
Kinds of flags, how they are read, the debt they leave behind, and the dark launch as a way to test infrastructure first.
- Part III
GitOps at Scale
Repository layout, multi-tenant clusters, secrets under GitOps, and reconciliation when the cluster drifts from git.
- Part IV
DevSecOps governance
Running the platform as a product, the DORA (DevOps Research & Assessment) delivery metrics across many teams, and what to build rather than buy.
§ 05, When it's readable