liveBook · Manning

Chapter 1: Why CI/CD isn’t enough

What you will learn in chapter 1 of Kargo in Action

The chapter introduces the promotion gap between CI and CD, why it makes releases risky, and where Kargo fits.

After this chapter you will be able to

Section by section

Introduction

The chapter introduces the promotion gap between CI and CD, why it makes releases risky, and where Kargo fits.

Key terms: CI, CD, artifact, promotion, desired state, Kargo, promotion control plane, GitOps agent, stages

1.1 The improvised layer in modern delivery

Lumen’s delivery pipeline shows how improvised promotion can deploy a fix successfully while leaving crucial questions about the release unanswered.

Key terms: CI, CD, GitOps repository, pre-prod, production, promotion, hotfix, verification suite, artifact, eligible to advance

1.1.1 A five-question test for the promotion gap

This section uses five questions to test whether an organization can readily verify and govern promotions between CI and CD.

Key terms: promotion gap, promotion control plane, separation of duties, artifact lineage

1.1.2 The everyday cost of the promotion gap

The section shows how missing promotion records make routine status checks slow, hotfixes risky, and rollbacks uncertain.

Key terms: promotion gap, image tags, environments, hotfix, pre-prod, payload, rollback, promotion record, known-good previous state, mutable tag

1.2 Where Kargo fits in the delivery stack

This section places Kargo between CI and a GitOps agent, defining promotion as a distinct responsibility in the delivery stack.

Key terms: CI, promotion, GitOps agent, artifact versions, stages, directed graph, source of truth

1.3 Three capabilities CI and CD don’t provide

1.3.1 Governed promotion

This section explains how Kargo makes promotion governed through three enforced gates and auditable records.

Key terms: auto-promotion policy, eligibility rules, approval gates, soaked, promotion, auditable

1.3.2 Queryable lineage

This section explains how Kargo’s artifact and promotion records make deployment history queryable and provide change-control evidence.

Key terms: queryable lineage, immutable records, revision identifiers, promotion, Kubernetes objects, garbage-collect, change control, evidence

1.3.3 Immutable artifact identity

This section explains how pinning an artifact to its digest keeps its identity consistent as it moves between environments.

Key terms: tag, digest, promotion pipeline, artifact reference

1.3.4 When Kargo isn’t the right fit

This section explains when open source Kargo is a poor fit, when its operational cost is justified, and how the commercial edition extends its reach.

Key terms: open source Kargo, Kubernetes-based delivery, GitOps agent, control plane, environment, compliance requirements, Kargo Enterprise, OpenTofu-aware promotion steps, custom steps, last-mile action

1.4 Walking a promotion end to end

The section traces one exact demo-app image version from discovery through automatic dev deployment and reviewer-gated production promotion.

Key terms: image repository, tag, exact image, promotion, dev, GitOps repository, manifests, Argo CD, verified, verified in dev

1.5 Summary

Where this is used later

Concepts explained in this chapter

Chapter 2: The layer nobody designed →

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.