liveBook · Manning

Governance

As explained in Kargo in Action

Governance is the set of policies, controls, accountability records, and decision procedures that constrain and document operational changes.

Governance constrains operational changes through policies, controls, accountability records, and decision procedures. In artifact delivery, it governs which versions advance between environments and leaves a record of those movements. section 1.0 section 1.0

CI builds and tests artifacts; CD deploys them. The gap between those jobs is promotion: choosing which artifact belongs in each environment and managing the desired state. When that work is improvised, teams may lack a useful audit trail or struggle to verify who approved a change and whether it was tested. section 1.0 section 1.0

A promotion control plane makes this governance explicit: it models environments as pipeline stages, tracks artifact versions in each stage, enforces advancement policies, and records movements as events. Kargo is one Kubernetes-native example, operating between CI and Argo CD or another GitOps agent. section 1.0 section 1.0

How Kargo in Action covers it

How deep it goes
Defines governance through advancement policies and event records, but stops short of detailing approval procedures.
Examples
Uses an unexpected image-tag discrepancy and a difficult-to-reconstruct approval or testing record as operational problems.
What you can do after
Understand how explicit stages, advancement policies, and event records make artifact movement auditable.
How it connects
Connects governance to artifact promotion, continuous integration, continuous delivery, Kubernetes, and GitOps.

Also explained in

Compare how 9 books explain governance →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Kargo in Action. The section links point to the parts of the book it draws on.