liveBook · Manning

Chapter 2: The layer nobody designed

What you will learn in chapter 2 of Kargo in Action

This introduction frames Lumen Retail’s promotion layer as the unintended result of reasonable engineering decisions, rather than careless work.

After this chapter you will be able to

What it builds on

Section by section

Introduction

This introduction frames Lumen Retail’s promotion layer as the unintended result of reasonable engineering decisions, rather than careless work.

Key terms: Lumen Retail, improvised promotion layer, intentional design

2.1 How Lumen built what it has

Lumen’s early promotion workflow shows why moving an image from pre-prod to production requires a selective configuration change and a decision that Git alone cannot make.

Key terms: CI, pre-prod, production, Argo CD Application, desired state, environment branches, merge, artifact references, rendered manifests, GitOps repository

2.2 What success cost

Checkout’s promotion safeguards improve releases, but scheduling and copying those safeguards across teams expose gaps in how the workflows track eligibility and test results.

Key terms: pre-prod test suite, test gate, production promotion workflow, soak, eligible, scheduled, polling, Argo CD, workflow, copies

2.3 What scale asked of it

The section shows how Lumen’s growing number of teams and environments exposed the limits of an improvised promotion layer, especially once a service’s path became a branching graph rather than a line.

Key terms: improvised layer, environments, teams, dev, smoke, perf, pre-prod, production, environment graph

2.4 What the layer never had

The section frames the coming gaps as limitations of Checkout’s job-built promotion layer that existed before scale made them costly.

Key terms: gaps, two-environment layer, jobs, scale

2.4.1 No view of the whole

This section explains why Lumen can see what an individual environment is running but cannot readily see a version’s progress across its promotion path.

Key terms: Argo CD, deployment question, reconstruction, shape of the graph, where each version is within it

2.4.2 Nothing is watching when nothing is running

This section explains why finite CI jobs cannot continuously watch for changes in promotion eligibility, leaving Checkout’s polling job to act as an improvised control loop.

Key terms: CI job, promotion, eligibility, soak, polling job, control loop

2.4.3 Nothing shared between teams

The section explains why legitimate team-specific promotion requirements do not justify duplicating promotion machinery, and why a shared workflow only partly solves the problem.

Key terms: machinery underneath, health, test result, version, soak, shared workflow, job, promotion control plane

2.4.4 Nothing an auditor can read

The section shows why Lumen can reconstruct approval evidence for a SOC 2 Type II audit but cannot reliably demonstrate that its varied promotion gates enforced the promised testing control.

Key terms: SOC 2 Type II audit, observation period, system of record, automated control, gate, production manifests directory, path-filtered git log, artifact, approver, pull request

2.5 A different kind of system

Devon’s pilot shows how a continuously running promotion control plane replaces Lumen’s scattered jobs with queryable version state, shared machinery, promotion records, and a single governance surface.

Key terms: promotion control plane, controller, soak, stage, environments as a graph, version’s own recorded state, verification result, version, verified in pre-prod, advance

2.6 Summary

Where this is used later

Concepts explained in this chapter

← Chapter 1: Why CI/CD isn’t enough Chapter 3: Getting started with Kargo →

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.