liveBook · Manning

GitOps operator

As explained in Kargo in Action

A system that continuously compares declared version-controlled state with actual runtime state and applies changes to reconcile them.

A GitOps operator watches a configuration repository and reconciles the cluster with its declared state. Its work begins when configuration changes and ends when the cluster matches. It does not build artifacts or decide which version belongs in each environment; promotion handles that middle layer. section 1.2

Figure 1.2 The three-layer Kubernetes delivery stack. CI produces artifacts; Kargo governs their promotion across environments; Argo CD reconciles the cluster state with what Git declares. Each layer has a single focused responsibility, and Kargo is the only one that addresses which artifact version belongs in which environment.
The three-layer Kubernetes delivery stack

The delivery-stack diagram distinguishes CI artifact production, promotion between environments, and GitOps reconciliation of cluster state. section 1.2

How Kargo in Action covers it

How deep it goes
Defines the agent’s start and end responsibilities, while distinguishing them from artifact building and promotion.
Examples
Names Argo CD as a reference implementation and Flux as another system in the same layer.
What you can do after
Understand how GitOps reconciliation fits alongside artifact production and promotion.
How it connects
Connects GitOps reconciliation with Git, CI, promotion, Argo CD, and Flux.

Also explained in

Compare how 3 books explain GitOps operator →

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.